-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"AIRMap" was not found in the UIManager IN "0.26.0" #3099
Comments
Yeah this issue is poorly edited but I also got this error by just updating the library, everything worked fine on 0.25.0 though - tested on Android, not tested on iOS yet. A little disclaimer is that I updated my react-native project manually from 0.59 to 0.60.5 and to 0.61.1 a few days ago, so I'm not sure if that could be related.
|
Yeah, the same thing happens with me |
In IOS works, but in Android i've got this error: "AIRMap" was not found in the UIManager |
Downgrade to 0.25.0 works fine |
|
Any other solution than downgrading? |
#3081 |
how do you properly downgrade react-native-maps? i did but now I get an error that says |
I just upgraded and received the same error. Any fixes yet? |
I believe the problem lies in Currently it contains this configuration:
while the valid configuration should looks like this:
Apparently when RN configuration was moved from project.json to separate file it was not converted to new specification. |
Thanks Skippone, that worked. Just made the change, reset and relaunched and maps working great! Appreciate the quick and more importantly, accurate reply! |
@skippone mind a PR? 😻 |
i have had that issue solved doing rborn what just did! tested on both devices it works like a charm if the config file is edited as done in the PR I sent! |
Well, someone was already faster than me :) |
@christopherdro can we make an "emergency release" with this fix? I just merged 🤗 |
I'm also getting this error and can't see any way to fix it. I think the problem might be happening with the react-google-maps module EDIT: I managed to get this work by using "expo-cli install react-native-maps" instead of "npm install react-native-maps@0.24.0" This made a bit of a mess though as everything else is installed using npm. |
anyone tell me how to handle this problem i have the same issue |
the issue is closed! as it is been solved in the PR! and will be soon released with the new version! @NoumanSakhawat @whiskyplausible |
@whiskyplausible downgrading is not an active solution! I have had been in the mindset of that too! I will say: you see the answer here of @skippone ! this should help you! use the present release for now! |
@rizwanatta please use the master for now, will be published as soon as @christopherdro has some time to look into :) |
I'm getting the same error on 0.26.1 / 0.25.x, RN 0.60.5 / 0.60.4. Both physical device and emulator, Android 8.0.0. Didn't try manual linking, though I'm assuming it would work. It's working properly on iOS. |
ok! the comment is a bit vague! can you tell me that are you trying an upgrade of the package in the project ! or is it a fresh project with packages and stuff! please! @eduardopelitti |
Hi @rizwanatta, It's a fresh project with the versions I specified, I was originally on 0.60.4 and 0.26.1 and got this error. I tried downgrading to 0.25.0, that didn't work, then I tried Maps 0.26.1 and RN 0.60.5, didn't work either. I followed the install steps for RN >0.60. Let me know if you need more info. Thanks in advance. Edit: Manual link works on Android. |
Hi! I am having this issue on iOS on 0.26.1. Any ideas? |
I'm also having this issue on Android on 0.26.1 with react-native 0.60.5 |
Skippone config change fixed it for Android for me, but i'm still getting AIRMap not found" error on IOS. Should that be changed for IOS as well? |
@tinymobile @wmonecke @RominHalltari @tinymobile @eduardopelitti have you all tried this watch @skippone's config stuff in your config files and match them with yours from if they are same then do this, please! 1: on iOS devices try building from XCODE after doing a Pod install if you have already pods setup then in case you are using google map you have to add the import and your API KEY feel free to reach out! FYI, :-) I just tested it on my new project of react-native 0.61 and 0.26.1 of react-native-maps! it works fine on both devices! |
I'm also having this issue on Android on 0.26.1 with react-native 0.60.5 |
Still missing AIRMAP on my Android with RN@0.61.2, never give up, mate 👍 |
I still having the issue with the version v0.26.1 |
Hey @javierfuentesm , your issue in Android or iOS , if Android can you share the root build.gradle? |
Any update on this? |
This issue is still coming up.
|
|
Perhaps this helps someone who's still struggling with a similar issue on Android. In retrospect, my issue was due to an incorrect Android Setup, specifically with package auto linkage. I had a faulty setup in MainApplication.java, the result of adding packages that require modifying this file (React Native Navigation and CodePush), which was overriding auto linking and causing this issue (notice that in my case manual linking made the issue go away). So specifically, in my project I had messed up with these lines when integrating RNN, resulting in broken autolinking:
Make sure Hope this points someone in the right direction. |
You probably just need to follow the react-native-maps set up process. I was missing the pod install etc steps https://github.com/react-native-maps/react-native-maps/blob/master/docs/installation.md |
Is this a bug report?
(write your answer here)
Have you read the Installation Instructions?
(Write your answer here.)
Environment
Steps to Reproduce
(Write your steps here:)
Expected Behavior
(Write what you thought would happen.)
Actual Behavior
(Write what happened. Add screenshots!)
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered: