Open cinzianicoletti opened 4 years ago
Thanks for the issue, I will check it asap.
Same for me:
System: OS: macOS 10.15.6 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Memory: 631.12 MB / 16.00 GB Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.16.1 - /usr/local/bin/node Yarn: 1.22.4 - /usr/local/bin/yarn npm: 6.14.6 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: Android SDK: API Levels: 23, 25, 28, 29, 30 Build Tools: 28.0.3, 29.0.2, 29.0.3 System Images: android-22 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom, android-26 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom IDEs: Android Studio: 4.0 AI-193.6911.18.40.6626763 Xcode: /undefined - /usr/bin/xcodebuild npmPackages: react: ^16.13.1 => 16.13.1 react-native: ^0.62.2 => 0.62.2 npmGlobalPackages: react-native: 0.61.5
check this out: https://github.com/facebook/react-native/issues/10009#issuecomment-347839488
try setTimeout
or a delay function before trying to access the Android API.
const delay = ms => new Promise(res => setTimeout(res, ms));
await delay(5000);
I have this abnormal problem. When I compile the application in debug mode everything works in the correct mode. The moment I create the apk and publish it for online tests, the alert to activate the GPS no longer appears. Anyone know what it is? Here the specifications:
I thank in advance who will want to help me.