-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
error in play store Pre-launch report: java.lang.RuntimeException: Unable to start activity ComponentInfo #41716
Comments
|
|
That's the root of your problem. |
if i check this, it leads to splash screen (we are using expo-splash-screen). |
Please report this issue against Expo then: |
Same problem here... |
Same here using NativeScript, so it's not rn specific. Anyone have a solution?
|
I'm experiencing this issue too. It apparently happens when requesting location permissions with PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.ACCESS_FINE_LOCATION) but only on Google Play console automatic tests. I haven't been able to replicate it on an emulator. |
I have exactly the same issue reported on same device, on my own app which is not using react-native. Looks to me like Google bug. |
Yes maybe Google just wants to test Android 14 development with each application on the market. |
I'm also seeing this problem, just like @ottor-o, I can't recreate it in an emulator. Only shows up in Play console report details. |
This is most probably coming from the Android feature of showing UI for device location settings when needed, not app location permission. |
I am having the same problem. I am also using uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/ Does anyone have a fix? Exception java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/com.google.android.location.settings.LocationSettingsCheckerActivity}: android.view.InflateException: Binary XML file line #3 in com.google.android.gms:layout/location_settings_dialog: Binary XML file line #3 in com.google.android.gms:layout/location_settings_dialog: Error inflating class android.widget.ScrollView |
Same issue here. I'm also not able to reproduce it on the emulator. Was someone able to fix it? |
I opened a bug for Google. On one hand if people here will add the information they have it can push Google to fix it. On the other hand if many examples will come from react-native code they might think this is react-native bug, which it is not. Anyway I guess marking yourself as impacted will help. |
Any workaround? |
Hello, all. I have maybe come up with a solution but I am not sure if it correct. The point is that it seems to have worked for me as Google Play Console is not telling me there is an error anymore. Apparently there are some instances where when you put android.permission.ACCESS_FINE_LOCATION into your AndroidManifest you must also put android.permission.ACCESS_COARSE_LOCATION in the AndroidManifest. See here for more information: https://developers.google.com/maps/documentation/android-sdk/location Like I said earlier, I do not know if this is the correct fix to the problem but it seems to work for me. |
I am not sure about this. First, as far as I understand this is not a permissions issue, but an Android device location settings UI issue. Second, I always had both permissions in the manifest. Third, I do not encounter the issue anymore with my yesterday's app upload. I think Google either fixed it, or removed the device from pre-launch tests. Nevertheless, they did not write any update in the bug-tracker issue mentioned above. |
I am not encountering the issue anymore either, I think DorBSoft is right and Google has done something to correct the problem on their end. |
I have also been encountering that issue with my flutter app. I just did a new upload waiting to see |
Description
in Pre-launch report we got an error, this is the report detail for the device
since the Android version is Android 14 (SDK 34), there is a possibility this issue will arise in the future.
it is related to the Location from the device, maybe permission issue or something else.
this is the error log:
i post this so the community aware the possibility of this issue, but i don't know what the issue category is.
React Native Version
0.71.4
Output of
npx react-native info
System:
OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Memory: 4.99 GB / 15.50 GB
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 18.9.0 - ~/.nvm/versions/node/v18.9.0/bin/node
Yarn: 3.6.4 - ~/.nvm/versions/node/v18.9.0/bin/yarn
npm: 8.19.1 - ~/.nvm/versions/node/v18.9.0/bin/npm
Watchman: 20220123.190932.0 - /usr/local/bin/watchman
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.21 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.4 => 0.71.4
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Snack, screenshot, or link to a repository
The text was updated successfully, but these errors were encountered: