Hi,
we built an app with Viewer Builder V18 and published two folios in our app (It was bulit with tools v18).
For our third folio we build an iPad2-folio and an iPad3-folio. It works fine.
We updated our app (Viewer Builder V20) in itunesconnect. Now you can get an update in the app-store.
Yesterday we published both versions of the third folio.
On an iPad2 it works fine. On an iPad3 the user gets the iPad2-version. The user doesn't get an information to update the app.
After updating the app the iPad3 shows the iPad3-content.
Now we update our tools (V20) an build the stacks for the iPad3-version again. We aktualize the iPad3-folio in the app.
We have the same result. On an iPad3 the user gets the iPad2-version. The user doesn't get an information to update the app.
After updating the app the iPad3 shows the iPad3-content.
What do we have to do that the iPad3-User gets the information that he has to update the app?
Thanks for your ideas,
Neele
Hey this might not work,
But when publishing do you publish the iPad 2 version first?
I've read something funny that you have to publish the iPad 1&2 version before you publish the iPad 3 version
not sure why - but that makes the prompt for the right content on the right device!
Hope this helps!
Tim
Hi,
thans for your idea. We solve the problem:
The old V18-app found a folio that works (the iPad2-Version, built with V18 tools), so there's no need to update the app.
We update the iPad2 and the iPad3 folio with V20 tools.
The user gets the information that there's an update for his folio.
When he tries to update his folio, he gets the information that he has to update the app for this update of the folio,
because the V18-app doesn't find any content that can be used, both folios are V20.
Neele
North America
Europe, Middle East and Africa
Asia Pacific