New app wants to replace an existing app on iPad
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: New app wants to replace an existing app on iPad
What you've done should work. Did you refresh profiles in XCode?
Look at the contents of the standalone app and check the info.plist file. Does it show the right info?
Look at the contents of the standalone app and check the info.plist file. Does it show the right info?
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- Posts: 135
- Joined: Thu Sep 13, 2012 10:25 pm
Re: New app wants to replace an existing app on iPad
Sorry to drag this on, but I'm still having problems.
Interestingly enough, when I look at my app's contents and dig into the "embedded.mobilprovision" file, I do see that the correct app ID is present. However, the "info.plist" file has my identifier as: "com.yourcompany.${PRODUCT_NAME:identifier}" and my version at 1.0 - and this is not what I specified in the standalone app settings in LiveCode.
It seems as if LiveCode is not writing the info.plist file correctly. However, I tried to change those values and in the info.plist file and install the app on my device, and I get an error: "The application does not have a valid signature."
Hmmm... Does any of this provide any additional clues?
I'd be terribly grateful for any advice folks might have.
Thanks
Joel
Interestingly enough, when I look at my app's contents and dig into the "embedded.mobilprovision" file, I do see that the correct app ID is present. However, the "info.plist" file has my identifier as: "com.yourcompany.${PRODUCT_NAME:identifier}" and my version at 1.0 - and this is not what I specified in the standalone app settings in LiveCode.
It seems as if LiveCode is not writing the info.plist file correctly. However, I tried to change those values and in the info.plist file and install the app on my device, and I get an error: "The application does not have a valid signature."
Hmmm... Does any of this provide any additional clues?
I'd be terribly grateful for any advice folks might have.
Thanks
Joel
-
- Livecode Staff Member
- Posts: 861
- Joined: Fri Feb 06, 2015 4:03 pm
Re: New app wants to replace an existing app on iPad
Hi Joel,
Which version of LiveCode are you using? Could it be the case that you have accidentally (or not) modified the IDE stack "revSaveAsIosStandalone"? Have you tried deleting the existing version of LiveCode and installing a fresh copy?
http://downloads.livecode.com/livecode/
Best,
Panos
--
Which version of LiveCode are you using? Could it be the case that you have accidentally (or not) modified the IDE stack "revSaveAsIosStandalone"? Have you tried deleting the existing version of LiveCode and installing a fresh copy?
http://downloads.livecode.com/livecode/
Best,
Panos
--
Re: New app wants to replace an existing app on iPad
Since the plist isn't reflecting changes, it sounds like a bug you should report. But before you do, make sure you are using the latest version of LC, it may have been fixed.
There are workarounds for now. The easiest is to manually delete the old app from the device before trying to install the new. EDIT: Never mind, this doesn't apply to your problem.
Or you can try including a corrected plist in the Copy Files pane of standalone settings. On Android this works to replace the default manifest, I haven't tried it on iOS but it may do the same thing.
Third, you can edit the plist in the built standalone, as you already tried to do. Altered apps can't be installed because the signature no longer matches, so you need to re-sign the app manually. There are a series of terminal commands to do that, but it's easier to use a utility like AppWrapper.
There are workarounds for now. The easiest is to manually delete the old app from the device before trying to install the new. EDIT: Never mind, this doesn't apply to your problem.
Or you can try including a corrected plist in the Copy Files pane of standalone settings. On Android this works to replace the default manifest, I haven't tried it on iOS but it may do the same thing.
Third, you can edit the plist in the built standalone, as you already tried to do. Altered apps can't be installed because the signature no longer matches, so you need to re-sign the app manually. There are a series of terminal commands to do that, but it's easier to use a utility like AppWrapper.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- Posts: 135
- Joined: Thu Sep 13, 2012 10:25 pm
Re: New app wants to replace an existing app on iPad
Hi all -
With everyone's help, I've come to a reasonable workaround. By manually editing the info.plist and then including it in a subsequent build (via the copy files pane), I'm able to deploy the app to my device.
However, I can fairly confidently say that for me, both LiveCode 8.0 and 8.1.0 (dp2) are not creating an info.plist that has the values for version and Identifier as specified in the Standalone settings pane.
Joel
With everyone's help, I've come to a reasonable workaround. By manually editing the info.plist and then including it in a subsequent build (via the copy files pane), I'm able to deploy the app to my device.
However, I can fairly confidently say that for me, both LiveCode 8.0 and 8.1.0 (dp2) are not creating an info.plist that has the values for version and Identifier as specified in the Standalone settings pane.
Joel
Re: New app wants to replace an existing app on iPad
Glad it worked for you. I think the team would appreciate a bug report about the problem.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com