More info on PhoneGap 2.9.0:
http://phonegap.com/blog/2013/06/26/p...
Upgrade!
If you come across any issues, let us know.
http://phonegap.com/blog/2013/06/26/p...
Upgrade!
If you come across any issues, let us know.
ryan, Developer
- 1538 Posts
- 132 Reply Likes
Posted 7 years ago
- 1 Post
- 0 Reply Likes
FileTransfer.onprogress doesn't fired for me. Tested it using the code example from api documentation.
- 1 Post
- 0 Reply Likes
Building apps only takes a few minutes but downloading from your website is excruciatingly slow. A single 10 MB app is taking 20 minutes to download from your servers after building!
ryan, Developer
- 1538 Posts
- 132 Reply Likes
This is likely your internet connection -- downloads are speedy for most.
- 134 Posts
- 0 Reply Likes
I have an old app that is essentially on life-support. It was built in the Phonegap 1.5 days and every now and then (when a change is needed) we try (or have to) bump the PG version to one that's recent (or just supported at all...).
Until this week, this app (ID # 94614) was using Phonegap 2.5 without issue. I had to make a minor change so I figured I'd upgrade to 2.9 while I was in there mucking about.
When using PG 2.9, my API AJAX calls are not working properly on Android. What do I mean by not working properly? This:
The exact same request, made via copy & paste into the integrated Weinre JS console, on an iOS and Android client running the app with PG 2.9.
If I downgrade to PG 2.7, they both get NULL. If I downgrade further (back) to 2.5, they both work. In case that's not clear:
What gives? Literally the only thing I'm changing between these tests is the version of PhoneGap that's being targeted, and the results are reproducible.
If it's relevant, the app is using jQuery 1.6.4. I could upgrade, but with no functional changes to the app, and the risk of introducing new bugs, why bother?
Unfortunately, I suspect (and will be doing further testing to verify) that there are bugs in the PGB implementation of PG 2.5 that would be considered critical blockers. If I recall correctly, the last time I used 2.5 there was an issue that caused insta-crash on iPad Minis, and sometimes the splash screen doesn't go away at all on iOS devices. If these are true, then my app is dead in the water until you either fix your 2.5 implementation or we figure out what's wrong with 2.9...
Until this week, this app (ID # 94614) was using Phonegap 2.5 without issue. I had to make a minor change so I figured I'd upgrade to 2.9 while I was in there mucking about.
When using PG 2.9, my API AJAX calls are not working properly on Android. What do I mean by not working properly? This:
The exact same request, made via copy & paste into the integrated Weinre JS console, on an iOS and Android client running the app with PG 2.9.
If I downgrade to PG 2.7, they both get NULL. If I downgrade further (back) to 2.5, they both work. In case that's not clear:
What gives? Literally the only thing I'm changing between these tests is the version of PhoneGap that's being targeted, and the results are reproducible.
If it's relevant, the app is using jQuery 1.6.4. I could upgrade, but with no functional changes to the app, and the risk of introducing new bugs, why bother?
Unfortunately, I suspect (and will be doing further testing to verify) that there are bugs in the PGB implementation of PG 2.5 that would be considered critical blockers. If I recall correctly, the last time I used 2.5 there was an issue that caused insta-crash on iPad Minis, and sometimes the splash screen doesn't go away at all on iOS devices. If these are true, then my app is dead in the water until you either fix your 2.5 implementation or we figure out what's wrong with 2.9...
ryan, Developer
- 1538 Posts
- 132 Reply Likes
The first thing to do is remove the 'browserOnly' attribute from your access elements. This intent of this is to force links to these domains to open in the system browser. Since you are doing an ajax call, not opening a link, this will be blocked.
The next thing I recommend is removing the protocols (http://) from your whitelists. I have seen these cause problems with whitelisting.
Lastly is the subdomains -- it appears that the subdomains attribute is not working properly on android at the moment (recently logged bug https://github.com/phonegap/build/iss...). We're working on a fix for this -- but in the meantime I believe you could get around this by removing the subdomains attribute and instead specifying the subdomain directly in your whitelist, like so:
Thanks for the detailed post!
The next thing I recommend is removing the protocols (http://) from your whitelists. I have seen these cause problems with whitelisting.
Lastly is the subdomains -- it appears that the subdomains attribute is not working properly on android at the moment (recently logged bug https://github.com/phonegap/build/iss...). We're working on a fix for this -- but in the meantime I believe you could get around this by removing the subdomains attribute and instead specifying the subdomain directly in your whitelist, like so:
<access origin="my.subdomain.mysite.com" />
Thanks for the detailed post!
- 134 Posts
- 0 Reply Likes
Thanks for the prompt reply! I'll try all of that stuff and get back to you...
- 134 Posts
- 0 Reply Likes
- 134 Posts
- 0 Reply Likes
And now it's broken again. Back to NULL on Android and real data on iOS. Are you guys actively working on it?
ryan, Developer
- 1538 Posts
- 132 Reply Likes
yes, sorry if we broke it. having a look again.
- 134 Posts
- 0 Reply Likes
Unfortunately my iOS app, which was functioning properly (as a dev build) now won't complete building with the prod signing key... I've uploaded the key files twice and verified I'm using the correct password. What's going wrong?
ryan, Developer
- 1538 Posts
- 132 Reply Likes
Looks like your iOS provisioning profile has expired.
Also, I've reverted the tweaks we tried today regarding android whitelists. So it should be working again in the state when you said all was well. Sorry for the inconvenience, we'll continue working on this to make this consistent.
Also, I've reverted the tweaks we tried today regarding android whitelists. So it should be working again in the state when you said all was well. Sorry for the inconvenience, we'll continue working on this to make this consistent.
- 134 Posts
- 0 Reply Likes
Thanks for the update. That did the trick. Do you have any plans to improve the error messages for build fails?
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers



