Thanks @Taifun & @Anke!
I found my mistake: the WP site has protected access by password, and the cookie is not saved after the first access. As a result, the 4.2k file is an HTML file of the protected page info!
Sorry for the noise here, and thanks again, @Anke, for this absolutely useful extension!
By the way, if you have any idea how to save the protected access cookie, I'd appreciate it.
08-20 21:06:17.165 27909 27909 E AndroidRuntime: Process: appinventor.ai_bioanalizer_com.Analizer, PID: 27909
08-20 21:06:17.165 27909 27909 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{appinventor.ai_bioanalizer_com.Analizer/appinventor.ai_bioanalizer_com.Analizer.Screen1}: java.lang.SecurityException: appinventor.ai_bioanalizer_com.Analizer: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts
it looks like you are using an extension, which not has been updated to SDK 34
and more from logcat
08-20 21:06:17.165 27909 27909 E AndroidRuntime: Caused by: java.lang.SecurityException: appinventor.ai_bioanalizer_com.Analizer: One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.os.Parcel.createExceptionOrNull(Parcel.java:3087)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.os.Parcel.createException(Parcel.java:3071)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:3054)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2996)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:5684)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1868)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.app.ContextImpl.registerReceiver(ContextImpl.java:1804)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.app.ContextImpl.registerReceiver(ContextImpl.java:1792)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:765)
08-20 21:06:17.165 27909 27909 E AndroidRuntime: at de.bodymindpower.downloadtoasd.DownloadToASD.(DownloadToASD.java:58)
Let me respectfully disagree
From the stackoverflow link
As discussed at Google I/O 2023, registering receivers with intention using the RECEIVER_EXPORTED / RECEIVER_NOT_EXPORTED flag was introduced as part of Android 13 and is now a requirement for apps running on Android 14 or higher (U+).
If you do not implement this, the system will throw a security exception.
Well, I think I won't continue to adapt my extensions to these idiotic targetSdkVersion restrictions. I've done that long and often enough. Now it's someone else's turn. There are a number of good alternatives to my extension.
Fortunately, I have nothing to do with this ridiculous annual SDK circus on iOS.