I'm getting the same old build no matter what I do, including generating a new app from a new Phonegap Build account! When I download the app, its Info.plist file is the old one with old data.
This is not my first hybrid App. Moreover, I've been able to build this app for Android and also for iOS. In fact, I've been already able to send it to Apple Store. The problem is that it was rejected, I've had to review some details, and now I need to change the "bundle versions string, short" and "bundle version" to a higher number in order to submit it again to Apple Store. I've changed config.xml accordingly but PG Build keeps generating the same old bundle with the old version numbering after I build the new code. I've cleared caches, used different browsers, connected from different IPs, and as I said, even user a different account at Phonegap Build.
I'm NOT using Phonegap Desktop App.
My App ID is 1987314.
This is not my first hybrid App. Moreover, I've been able to build this app for Android and also for iOS. In fact, I've been already able to send it to Apple Store. The problem is that it was rejected, I've had to review some details, and now I need to change the "bundle versions string, short" and "bundle version" to a higher number in order to submit it again to Apple Store. I've changed config.xml accordingly but PG Build keeps generating the same old bundle with the old version numbering after I build the new code. I've cleared caches, used different browsers, connected from different IPs, and as I said, even user a different account at Phonegap Build.
I'm NOT using Phonegap Desktop App.
My App ID is 1987314.
- 14 Posts
- 0 Reply Likes
- confused
Posted 4 years ago
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
including generating a new app from a new Phonegap Build account!So, the old app is not returned by your old account, only. It is unlikely that the PGB server returns the old (cached) app in multiple accounts.
I've cleared caches, used different browsers, connected from different IPsSo, it's unlikely that the old app is cached somewhere locally.
That leaves only one option: you are uploading the same set of sources by mistake. You may think you're sending a new set with a new config to PGB, but in fact you aren't.
OR
You aren't any more (after you did once) AND you have Hydration switched on (which will cause config changes to be ignored).
- 14 Posts
- 0 Reply Likes
Thanks for your answer! It seems that the build does take the code, but the changes I made to config.xml for setting the bundle and build numbers for iOS are not being used and the generated Info.plist is always showing version 1.0.0. That's why I thought it was always the same build file.
That's a different problem, so I'll ask it elsewhere. Thanks again.
That's a different problem, so I'll ask it elsewhere. Thanks again.
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
It might be Hydration. If you make config changes, be aware that you must disable Hydration first.
- 14 Posts
- 0 Reply Likes
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
Yes. It's disabled.
Can you confirm that both index.html and config.xml are in the root directory ("/") of your zip file?
Can you confirm that both index.html and config.xml are in the root directory ("/") of your zip file?
- 14 Posts
- 0 Reply Likes
Yes, they are.
And this is the beginning of my config.xml file:
And this is the beginning of my config.xml file:
<?xml version='1.0' encoding='utf-8'?>
<widget xmlns = "http://www.w3.org/ns/widgets"
xmlns:gap = "http://phonegap.com/ns/1.0"
id = "xx.xxxxxxx.app"
versionCode = "110"
version = "1.1.0">
<gap:platform name="ios" />
<gap:config-file platform="ios" parent="CFBundleVersion">
<string>1.1.0</string>
</gap:config-file>
<gap:config-file platform="ios" parent="CFBundleShortVersionString">
<array>
<string>1.1.0</string>
</array>
</gap:config-file>
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
You should not need the CFBundleVersion config-file entry. Try deleting it for test purposes.
Also, I seem to recall that the CFBundleShortVersionString should:
- not contain an array
- be a string of digits only (not too sure, but I never add dots myself)
So, I'd suggest:
Also, I seem to recall that the CFBundleShortVersionString should:
- not contain an array
- be a string of digits only (not too sure, but I never add dots myself)
So, I'd suggest:
<config-file platform="ios" parent="CFBundleShortVersionString">
<string>110</string>
</config-file>- 14 Posts
- 0 Reply Likes
It doesn't work! I've changed other lines to check that PB Build is using my config.xml. It is, but the Info.plist file keeps showing version 1.0, bundle version 1, where config.xml is defining 1.1.0 the way you proposed.
I'm really stuck with this. Any other idea of what might be happening? Maybe some syntax error? The XML file seems well formed.
Thank you very much for your support!
I'm really stuck with this. Any other idea of what might be happening? Maybe some syntax error? The XML file seems well formed.
Thank you very much for your support!
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
As I wrote already, you should not need CFBundleVersion.
The version attribute in the widget element, along with the bundle version in iTunes should be sufficient to satisfy Apple.
If the config-file entry for CFBundleShortVersionString (or even CFBundleVersion) have no result, something completely different might be causing this, like an info.plist file included in the assets, another config.xml present, or a wrong directory structure.
If you zip file is available online somewhere, please post its url and I'll be happy to have a look.
The version attribute in the widget element, along with the bundle version in iTunes should be sufficient to satisfy Apple.
If the config-file entry for CFBundleShortVersionString (or even CFBundleVersion) have no result, something completely different might be causing this, like an info.plist file included in the assets, another config.xml present, or a wrong directory structure.
If you zip file is available online somewhere, please post its url and I'll be happy to have a look.
JesseMonroy650 (Volunteer), Champion
- 3325 Posts
- 122 Reply Likes
Just the example used on the link. Follow the link. It is just an example.
- 14 Posts
- 0 Reply Likes
Dear Petra and Jesse,
I've tried everything you suggest and many more combinations and I'm still not getting but Build Number (aka CFBundleVersion) = 1. I need that number to be 2.
Petra, my zip file is here: http://fitxers.indret.webfactional.co...
If you could have a look I'd be very grateful.
I've tried everything you suggest and many more combinations and I'm still not getting but Build Number (aka CFBundleVersion) = 1. I need that number to be 2.
Petra, my zip file is here: http://fitxers.indret.webfactional.co...
If you could have a look I'd be very grateful.
JesseMonroy650 (Volunteer), Champion
- 3325 Posts
- 122 Reply Likes
@David
the file was not found.
Jesse
the file was not found.
Jesse
- 14 Posts
- 0 Reply Likes
I'm sorry!! Wrong URL. Here it is: http://fitxers.indret.webfactional.co...
Petra V., Champion
- 7794 Posts
- 1391 Reply Likes
Here's some feedback on the zip file:
1. Your zip contains two main directories: _MACOSX and DiaSporas.github
However, PGB requires both config.xml and index.html in the root of your zip, so make sure these directories disappear
2. You include an old cordova.js in your assets. You can't do that.
Remove the file. This is most likely the main cause of the trouble
3. You are missing splashes for the larger displays, like iPhone6(+). You should add them
4. You are using the old names for plugins. At npm, they are named differently (cordova-plugin-xxxx)
Also, you are using a very old version of the splashscreen plugin. Replace by the latest version of cordova-plugin-splashscreen.
For iPad, add cordova-plugin-statusbar
5. You have many 'feature' elements, which are obsolete, now. Read the latest Blog article on that.
These should be removed.
6. You have a config-file entry for CFBundleVersion twice, with different versions. IMHO, you don't need any of them, but at least you should at most have one.
7. You have SplashScreenDelay twice, with different values. That makes little sense.
8. You have a copy.bar file in your assets, which has no business there
9. You have several 'makefile' files in your assets, which shouldn't be there
1. Your zip contains two main directories: _MACOSX and DiaSporas.github
However, PGB requires both config.xml and index.html in the root of your zip, so make sure these directories disappear
2. You include an old cordova.js in your assets. You can't do that.
Remove the file. This is most likely the main cause of the trouble
3. You are missing splashes for the larger displays, like iPhone6(+). You should add them
4. You are using the old names for plugins. At npm, they are named differently (cordova-plugin-xxxx)
Also, you are using a very old version of the splashscreen plugin. Replace by the latest version of cordova-plugin-splashscreen.
For iPad, add cordova-plugin-statusbar
5. You have many 'feature' elements, which are obsolete, now. Read the latest Blog article on that.
These should be removed.
6. You have a config-file entry for CFBundleVersion twice, with different versions. IMHO, you don't need any of them, but at least you should at most have one.
7. You have SplashScreenDelay twice, with different values. That makes little sense.
8. You have a copy.bar file in your assets, which has no business there
9. You have several 'makefile' files in your assets, which shouldn't be there
- 14 Posts
- 0 Reply Likes
Thank you very much, Petra!! What an incredible response. And it did the trick. I'm even embarrased to say that I think 6 was the main problem. The stupidest bug. But thank you very much for all the other comments. I'll take them into account, for sure.
Related Categories
-
PhoneGap Build
- 15111 Conversations
- 275 Followers




