Some extra info.
The first viewer was created with WoodWing, compiled with Xcode. I checked and the BundleShortVersionString of the first viewer is 2.1. But even if I select 2.5 for the update version in iTunes Connect, it still gives me the same error.
Now there is no way of changing this version number with a DPS build is there?
We saw this error message back in the prerelease days when the Viewer Builder first came out. Some apps that were created manually had a higher version number than the Viewer Builder version. The Viewer Builder automatically increases the version number with each new build. The workaround was to keep building new updates of the app in Viewer Builder until the version number is higher than the submitted version number.
I will ask the client for his versions.
I tried this out myself. I have a personal app with number 184.108.40.206.39108, when rebuilding this, the number became 220.127.116.11.39108 and again 18.104.22.168.39108.
So the fourth number is changing. Suppost I need a version 2.5.xxxxx, that would mean I need to rebuild the app 187 more times before reaching the 2.5.xxxx mark. I understand DPS is a closed system (that's why everyone can use it), but are there any other options? Because that's something I just cannot ask my client to do.
I know that you can change this version in the info.plist file when unzipping the build. But re-zipping the file makes the file corrupt for upload. Is there a way to re-zip this in a good manner so it doesn't get corrupt? If yes, that would let change the version number myself without the rebuild marathon.
Thats great news, Bob. I'll contact Matt this monday.
I'm actually working as a DPS and WoodWing reseller. This means that, apart from giving demos and training+technical support, we are now starting with the migration of WW content (ofib files) and updated adobe viewers. So I'm just thinking that we might come accross the same issue with another client at a later stage. But I hope not.
I'm Bart's colleague, busy with WoodWing migrations and yes indeed, we will have this issue with all of our customers updating their WoodWing Readers to Adobe Viewers, but also all other WoodWing partners and customers.
If someone from Adobe can edit the version number on the Viewer Builder server, it's a nice solution, but he will probably have a lot of work in the next months.
Another solution would be to give us the possibility to modify the CFBundleShortVersionString in the Viewer Builder, while creating the app.
The Viewer Builder could suggest the number, with increment, like it does now, but it should be editable, with a warning "take care, has to be greater than previous version".
It would be perfect to have this implemented in the Viewer Builder of sprint 19.
Or, if you don't want to give this possibility to every users, make a special version for WoodWing migrations.
Today I received a screenshot of the clients' Viewer Builder.
The app version is 22.214.171.124.39108
The marketing version is 1.0.1
We were talking about changing the CFBundleShortVersionString version number before, and I was refering to this long number (because I assumed that was it). But now (while seeing this screenshot) I'm getting the feeling that it's the marketing version that needs a change? Because the updated viewer of the client uses version 2.5 (which is higher than 2.3.xxx) but the client receives his error.
Can you confirm that it's actually the marketing version that needs to be changed?
I have the same problem, we built the first app for our client through WoodWing, now we want to update the app with the Adobe one. During the upload of the new app, created with the Adobe Viewer Builder we get this error code:
This bundle is invalid. The key CFBundleShortVersionString in the Info.plist file must contain a higher version than that of the previously uploaded version.
When we open the Info.plist we can see that the Adobe Viewer Builder creates 1.0.1 for the Bundle Version String short, while the older WoodWing app has 2.1.
Marketing version in Viewer Builder = Bundle Version String Short or ?
That means everybody who is changing from the WoodWing to the Adobe reader needs to go through Adobe?
I talked this over with Matt back in the day. He wrote a procedure to fix this issue which he made available to Adobe support. He asked that in the future people just contact gold support an ask for this procedure. The doc is called “Modify marketing/build version in Viewer Builder”, give this info to gold support and they'll know what to do.