Hi, I'm struggling to publish a simple app on Google Play that I built using MIT App inventor because of an issue with Cleartext traffic. I am unable to find this setting in MIT App Inventor to change it. Can anyone offer any advice? Many thanks.
Security and trust
Cleartext traffic allowed for all domains
Your app's Network Security Configuration allows cleartext traffic for all domains. This could allow eavesdroppers to intercept data sent by your app. If that data is sensitive or user-identifiable it could impact the privacy of your users.
Consider only permitting encrypted traffic by setting the cleartextTrafficPermitted flag to false, or adding an encrypted policy for specific domains.
Thanks for the quick reply. I did see that entry but it refers to a warning but I get an error and I was thinking that it was the reason I am unable to publish? It clearly says it's an error and not a warning....I have warnings as well but I can ignore those.
Here's the line I get on the Pre-Launch Overview
This shouldn't prohibit publication, but who knows, Google changes the rules pretty much at random with little fanfare. Let's see if others complain about this.
Note: Just because we permit unencrypted connections doesn't mean that connection are unencrypted. That is up to the app author as to whether they use "http" or "https" urls...
Don't you think it is time you shared your code. Someone might see what might be causing issues that bother GooglePlay's criteria.
What does this mean? You get that response when you attempt to publish the app or does that happen when you 'run' the app or something else (like try to download you app from GooglePlay)?
I create an internal test of the app. It says it's available to internal testers.
I get the link from a phone that I've setup as a tester and I get to this screen.
Are you doing an internal test on GooglePlay too? Do you get exactly the same response reported by Bernkev?
Bernkev said that regarding his issue, he " come back today everything works fine" just by trying again. This suggests this is a GooglePlay issue that might have been fixed just by waiting.
