weverwijk
commented
1 year ago We have the same issue. Users would like to use an Samsung Galaxy 8. This is not possible now.
Closed kiskoza closed 1 year ago
weverwijk
commented
1 year ago We have the same issue. Users would like to use an Samsung Galaxy 8. This is not possible now.
kiskoza
commented
1 year ago Hi. I think I found the solution and it has nothing to do with the error I described above. I can still see the mentioned stack trace with logcat, but it's not the one causing the crash.
The real one was this one:
2022-09-05 19:40:43.426 4237-4237/dev.hotwire.turbo.demo E/AndroidRuntime: FATAL EXCEPTION: main
Process: dev.hotwire.turbo.demo, PID: 4237
java.lang.IllegalArgumentException: reasonPhrase can't be empty.
at android.webkit.WebResourceResponse.setStatusCodeAndReasonPhrase(WebResourceResponse.java:139)
at android.webkit.WebResourceResponse.<init>(WebResourceResponse.java:77)
at xl.a(PG:292)
at afG.handleMessage(PG:67)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6669)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)While I was searching for the meaning of this error trace, I found a chromium bug, which was fixed around 2019. I updated my Chrome on my emulator and the problem went away (as described here)
Sorry for the false alarm, I'm closing this off
Hi. I was trying to run the demo with an emulator, but it was crashing over and over.
I opened up logcat and got this stack trace
``` Rejecting re-init on previously-failed class java.lang.ClassBased on the error messages above I found a reference page which says the missing class was introduced in API level 29. I checked my emulator and it was running on API 28, which is allowed by the both the package's and the demo's gradle file. When I switched over to API level 29, it went smoothly.
Unfortunately I'm not too familiar with android development, so the best I can do is move the minSdkVersions up to 29, but I hope there's a better solution than dropping support for older phones.
System details
``` > git status HEAD detached at 7.0.0-rc12 nothing to commit, working tree clean > gradle --version ------------------------------------------------------------ Gradle 6.5 ------------------------------------------------------------ Build time: 2020-06-02 20:46:21 UTC Revision: a27f41e4ae5e8a41ab9b19f8dd6d86d7b384dad4 Kotlin: 1.3.72 Groovy: 2.5.11 Ant: Apache Ant(TM) version 1.10.7 compiled on September 1 2019 JVM: 1.8.0_312 (Temurin 25.312-b07) OS: Linux 5.4.0-40-generic amd64 > avdmanager list target id: 2 or "android-28" Name: Android API 28 Type: Platform API level: 28 Revision: 6 ---------- id: 3 or "android-29" Name: Android API 29 Type: Platform API level: 29 Revision: 5 ```