breautek commented on issue #1754: URL: https://github.com/apache/cordova-android/issues/1754#issuecomment-2566679877
> Can this situation be caused by the fact that when building the project I used not recommended version of Android Studio Android Studio Ladybug | 2024.2.1 Patch 3. Although the recommended Android Studio Jellyfish. Android Studio Ladybug should be fine and is what I'm using currently as well for my projects. The Android Studio IDE itself doesn't usually matter as much as long as you ignore the IDE recommendations of upgrading the Android Gradle Plugin, as doing so usually involves breaking changes that requires refactoring in the gradle build scripts. Cordova-Android is only tested against a particular AGP version that the cordova-android release is configured as the default. > I did the debugging as you described above, but there were no javascript errors. If there were, it would be easier ). And in my Android Studio I can't reproduce the error that other users are displaying, because on my phone and on emulators the app works fine. If you can't reproduce locally then that's going to have to be your priority. There isn't much that Apache can assist if there is no understanding on how to even reproduce your issue. What I can do is offer some knowledge. What we know so far is: > The splash screen starts and that's it, it doesn't load any further. Can you tell me what could be the reason? There are several reasons why the app may "stop" loading, usually something has interrupted the loading process likely due an error, either on the native side or the javascript side. But if the app doesn't close, then it is just "hanging", then it is likely not a native crash since native crashes tends to ungracefully kill the application. It can still be a caught native error, or a javascript error. You've told me that on your devices or emulators that you have used, there is no JS error or errors found in logcat, and you've also told us that you're unable to actually reproduce the error yourself. **This tells us that the issue is likely "environmental".** That is an issue that only produces in a specific environment, or device configuration. If your web application (including any dependencies that you might import) uses modern javascript (anything newer than say ECMAScript 2015, aka ES6) you might run into issues here, especially on older devices running older webviews, or on devices that are simply have an out-dated `Android System WebView`. Try running your device on an API 24 simulator without logging into Google Play, which will give you a near AOSP-factory webview version, which will be dated. If the issue reproduces then, then it suggests that the actual problem is using a JS feature that isn't actually supported by the webview on that device. An API 24 simulator will have Webview 52 which will have good (95%+ support for ES6), but ES7/ES8 features typically are only implemented in version 58-60+ So testing an API 24 (or whatever what your min SDK) will help rule out Javascript support issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
