CLEARTEXT communication to 192.168.0.101 not permitted by network security policy
Hi All, I tried to implement the JRDC2 implementation of Erel in one program. The implementation of Erel is in the below URL: https://www.b4x.com/android/forum/threads/b4x-jrdc2-b4j-implementation-of-rdc-remote-database-connector.61801/ I get the following error: ResponseError. Reason...www.b4x.com
Apps that run on Android 11 but target Android 10 (API level 29) can still request the requestLegacyExternalStorage attribute. This flag allows apps to temporarily opt out of the changes associated with scoped storage, such as granting access to different directories and different types of media files. After you update your app to target Android 11, the system ignores the requestLegacyExternalStorage flag.
I can't set the sdk lower because Google will then not accept the app in the Play Store.If your app is for personal use set
in the Manifest.B4X:targetSdkVersion="26"
I have had sdk set to 31 for quite a while and it has worked fine. I have not changed the sdk version and it just won't work now.Storage updates in Android 11 | Android Developers
developer.android.com
It does not work with targetsdk set to 30 or more i guess
I am unable to stream mp3's from non-ssl sites now. Has something changed?
I have had sdk set to 31 for quite a while and it has worked fine. I have not changed the sdk version and it just won't work now.
The issue is not with the App but with the requirements of MediaPlayerStream. According to the B4X documentation:I've attached an updated app
According to the native documentation the online resource must support progressive download.
So it looks like it is a server-side configuration issue as it pertains to small files on the HTTP server (if it otherwise supports accept-ranges). If you download the mp3's of both sites, they are the same size. The HTTP server does not support accept-ranges for that particular file and the HTTPS one does. My conclusion was that the HTTP server itself does not support accept-ranges, but it could be that it does not support accept-ranges for small(ish) file sizes (or maybe, for some reason, just this file). In the end, not having an accept-ranges in the returned header is why the file from the HTTP server fails to play with MediaPlayerStream.the site does have an accept-ranges header, but the particular mp3 is short and appears to have been obtained with a simple get.
It depends. It could just be a configuration issue on the server that can either be changed by the user or maybe through a support ticket.I'm assuming at this point that a free web host will not suffice for what I want to do in my app. I've tried quite a few free web hosts and noce of them seem to allow insecure mp3 streaming. I assumed because of the lack of accep-ranges in the returned header.
a free web host will not suffice for what I want to do in my app
Try this (not guaranteed to do anything):It could just be a configuration issue
2) Add the following content(s) to the file:.htaccess
<IfModule mod_headers.c>
Header set Accept-Ranges 'bytes'
</IfModule>