-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Map shows correctly and so does location in EMULATOR. Built app crashes on MapView #11360
Comments
Hey @cratag, is the crash occurring when you run the apk in the emulator as well or on a physical device? |
Hey Adam, I didn't check the apk in the emulator. I'll check it out right now |
@cratag Try to check whether your apiKey has enabled Maps SDK for Android in Google Console. If it is not the problem, then upload the logs from built apk. Most probably the error message is in logs, you just need to read it) |
Well I've managed to create the logcat. I've seen an error that said invalid key so I made a new key and now I don't see the error in the logcat, but the app crashes nevertheless once the map is shown. Logcat is too long so here's a link for the full LOGCAT.TXT FILE and here's an extract of the logcat from the first time "MULTICOBERTURA" (my app) is shown, which I found relevant:
|
Please, if anyone knows what I'm doing wrong, that would be really helpful. |
I think I've added more info, shouldn't the tags be removed? |
Happy new year to everyone. Anyone knows? |
What kind of additional info does this need? I really need help, I don't know if I'm not showing the necessary info or if it is that no one knows the answer :( |
@cratag - you have probably not configured it as explained on https://docs.expo.io/versions/latest/sdk/map-view/#configuration |
Thank you. I've just did all of the steps again with a new account, project and organization. I no longer have the "An error occurred retrieving ClientID" error in the google API credentials so there's hope. APK is building right now. Will give further notices Thank you all |
It doesn't work. Same error as before. I don't think it's related to API key. |
I have the same issue, it works in the managed workflow when published to expo, but when deployed to Google store app, it crashes as soon as I tap the map screen. |
Hey, I've fixed it, so I'll give you a heads up: if the app crashes, then it's not about the API KEY from Google. If the key does not work, then the map renders GREY without content, but won't crash. So lets do this step by step:
|
Hey! Thanks a lot for the reply. I went step by step and I actually installed the APK file in my phone, tested it that way and it worked fine at first. Then, uploaded it to the Play Store and got the map to show grey. I tried with the SHA-1 cert from the Play Store and then it showed up. Thanks again for the reply and the help. Hopefully other people having the same issue see it here. :) |
My map works perfectly on the emulator, showing the actual location and map working.
As soon as the map should show in the apk, it crashes and restarts the app.
I’ve configured a separate screen to isolate the issue. I’ve added a text that says “Longitude” and “Latitude”, and it shows the numbers, ergo location is working.
In this screen I’ve made to test the issue, as soon as I click the open map button the app reloads. If I click the map button, a map renders but doesn’t go to the location position.
2
2720×1280 47 KB
Does anybody know anything about this? I’m sure I’ve already configured the API key correctly but maybe I missed something?
app.json
I've made a post in the expo forums but they couldn't help me.
Please tell me if there's anything else I can update for you. Thanks in advance
The text was updated successfully, but these errors were encountered: