I use to send build to codenameone for year, but suddenly all the newly android build apps is not working with http protocol, getting "java.io.IOException: Cleartext HTTP traffic to domainname.com not permitted."
I search through google but not finding any solutions about android for codenameone.
I understand apple had force this to https, but not android.
Can somebody help here?
Try to play around the codenameone setting page for this project to add a build hint
android.xapplication=<application android:usesCleartextTraffic="true" />
But not working as well.
We migrated to API level 28 over the weekend as required by Google. This broke compatibility on some fronts as is typical to them... That's one such front.
What you're looking for is android.xapplication_attr but the argument isn't correct either:
android.xapplication_attr=android:usesCleartextTraffic="true"
Related
I use osm in my AngularJS app and in Google Chrome browser I get the following messages
So I do not have access (any more) to the tiles. Three days ago it worked fine. If I open the application in Firefox everything is fine and works.
Is this an adjustment in Google Chrome or how I can find out what I have to do in order to get it work with Google Chrome anymore.
Not sure if this will help, but from PINTOSTACK, in
https://help.openstreetmap.org/questions/83887/unable-to-download-tiles-403-forbidden
"Maybe this will help someone else, for those using leaflet, we fixed it by changing http to https on the tileLayer png. Seems to work on localhost in Chrome & Edge."
I made the change and this worked for me.
You are not adhering to the tile usage policy. That's why your access denied message links to that policy.
OSM became stricter in enforcing the policy recently.
Could be related to another provider that slashed It's free tier by 99% recently and therefore users flocking to OSM.
As the tile usage policy stats: "OpenStreetMap data is free for everyone to use. Our tile servers are not."
(see: https://operations.osmfoundation.org/policies/tiles/ )
So please follow that policy closely if you use OSM for light use. For use in a business context or an app you shouldn't use those tile servers by the OSMF anyway (see the usage policy that asks you not to hardcode the tile.openstreetmap.org URL into an app).
Alternatives can be found here: https://wiki.openstreetmap.org/wiki/Tile_servers
If your angular application is producing only light use and not used for business contexts, check your dev tools in Chrome about the User-Agent and referrer your angular app is sending.
Hope everything is fine.
I have an old ionic v1 project.
The project was using sms features.
however after google update:
I received
Issue: Violation of the Permissions policy
We only allow apps to access Call Log or SMS data for permitted uses and only to enable the app’s core functionality
Google has removed my app.
I need to rebuild it again after fixing the issue.
Now we have ionic v 4.1.0.
My project structure is missed up.
The earlier developer, was using cord-ova, ionic,phone gap... etc
Any suggestions ?
I was finding myself in a similar situation. The best and fastest way in this case would be to start a new project while you have the other one open and try to copy as much code as you can. I hope that helps, good luck!
When will SSL support for custom domain be available within the developer console, instead of having to go over to Google Apps? I read somewhere it says Q3 of 2015. But seems like people have some ways of getting that to work already. Is it a private beta feature?
Building some apps for a client and they can't get their Google Apps account to work and we already have the custom sub-domain mapped to the GAE, and just need the last piece. Help!
This is the tracking issue, indeed Q3 seems to be more likely: https://code.google.com/p/googleappengine/issues/detail?id=10794
FWIW, I detailed a bit my solution to get things working via Google Apps in this Q&A: AppEngine subdomains to modules without wildcard mapping, maybe it can help with your customer's problems in the meantime.
My questions is in two folds: issue with app engine:update and with the app cfg.sh.
I looked on the web and could not find any workaround or potential answer that could help me fixing this issue.
My application is working with not much issue locally. Time now to give it a shot on production and upload it to google app engine. At first I tried doing this by using the 'app engine:update' from gradle (I'm using Android Studio). The execution failed with the following error message: "toolkit not found: apple.awt.ctoolkit. Why is this toolkit required and where can we find it?
While searching on the internet there were suggestions to use the appcfg.sh script to upload the application. It seemed to work at first until it asked for email and password. I used the exact same email/password I use to connect to goole-appengine and for some reasons it does not work.
Thanks.
After few hours investigating this issue I found out what the issues were. First thing, my account was compromised and received an email from Google. All I had is to confirm that was me trying to upload application to GAE. Secondly, my primary email address linked to my Google account belongs to another ISP. There is a security feature to disable and for security being a bit more loose. Creating a gmail account did the trick.
I'm hosting my website using Google App Engine. It's a pretty simple website, but I've got some javascript drawing to a canvas element, which I'm trying to test on my iPhone. I'd also like to take a crack at reworking my CSS for mobile. However, I can't access http://localhost:8080/ (which is the url that GoogleAppEngineLauncher spits out when I run the app locally) from my phone. This seems obvious.
Unfortunately, it seems that Mountain Lion has removed the web sharing preference from system preferences. I found at least two different sites with "solutions" for re-activating web sharing (Apache server?), but none of them seem to work in conjuction with Google App Engine... I also tried this preference pane, which also doesn't work. I keep getting "Safari cannot open the page because it could not connect to the server."
Sorry if this is a stupid question, I'm a relative noob to this stuff. Also, I see a lot of questions here on SO which seem related, but I think I'm still too uninitiated to understand how they're releated. Is there an extra step here that's GAE specific which I'm missing?
This isn't anything specific to your OS. By default, the App Engine dev server binds to the loopback interface, making it accessible only to your machine. If you want to access it from other machines, you need to pass the --address=0.0.0.0 flag to the dev server - which you can do in the launcher's preference pane.
As of March 2013 - the "address" argument has been renamed to "host" - (at least for Python version of the app engine)
--address=0.0.0.0 argument not working after upgrading to App Engine 1.7.6