Unable to load release profile build to device

Solar2D iOS
#1

Up until build 2511 we were able to upload all types of provisioning profiles builds to our test devices. 

When we moved to 2529, then tried 2555 and then the latest 2564 we are no longer able to upload a release profile build to a test device. It returns with the familiar error of mismatch between the provisioning profile entitlement and the compiled app entitlement.

We are still able to load ad-hoc builds. Needless to say we tried to regenerate all profiles etc. when falling back to 2511, we can upload the generated apk with release profile but this build does not support 64bit. we’re stuck.

The problem probably originated somewhere between build 2511 and build 2529.

We use devices with iOS8.1 version.

Our compilation Mac OS version is 10.10.

Does anyone else suffer from this problem?

I searched for threads on this issue but found nothing else on this forum.

#2

You should have never been permitted to use a release profile directly installed.  Developer and Release/AdHoc are the only two that can be put on a test device, unless you’re using Apple’s new TestFlight, which actually uses the Release/Store profile.

rob

#3

That’s not true Rob. Perhaps they did not intend to have that, but once you have a dev or an ad-hoc profile on your device, you can install a release version of that app on a test device. what troubles me is that we were able to verify that the release build is running properly on our test devices before and now we can’t. 

#4

My two latest apps have been rejected by apple due to bugs in game play. This is for a code that used to work in previous apps with no issues. When testing using the ad-hoc certificate everything seems fine. The problem remains that I can test on my device the distribution version as I used to.

I don’t know what you did to the build process for the release version but the problem seem to originate from there. 

#5

Seems I’m not the only one who found this issue. There are many comments on that here:

http://coronalabs.com/blog/2015/01/21/update-on-corona-ios-64-bit-support-and-plugins/#comment-503573

I suspect it also causes the problem we currently see in approving our app in apple review process.

We narrowed the problematic build down. The code we are trying to submit works flawlessly on build 2525, but fails for some reason starting from build 2526.

You have made some breaking change during build 2526, probably as part of making this fix:

  • Mac - Fix issues with building for TestFlight (beta-reports-active) and duplicate codesigning identities - casenums 37100, 37124

Please look into it. If you need me to provide the binaries to show the different behavior I can be reached at

info@tiltangames.com

www.tiltangames.com

Adi

#6

I have never been able to run a distribution app (non Ad-hoc) on a test device. I just did a build with 2576 and 2511 with a Store Distribution provisioning profile and both fail to install on an iPad iOS 8.1 device. I have both a developer profile and adhoc profile on the device.

I Googled the issue and found a Stack Overflow thread saying this worked at one time but is not longer the case:

This seems not to be the case anymore - e.g. AppStore provisioning profiles signed builds won’t install on devices with AdHoc provisioning profiles anymore. –  DotNetWise Feb 10 at 11:22

This answer is showing its age - it needs to be updated. The old behaviour may have been a bug… There’s always re-signing your app store builds to get the final build on a device. –  Rhythmic Fistman Feb 12 at 0:30

http://stackoverflow.com/questions/21019760/how-come-i-can-install-an-app-store-distribution-build-directly-on-my-device

#7

I just built our Fishes and MuitiPuck sample apps with App Store Distribution and uploaded them to iTunesConnect. I tested the apps on an iOS 8.1 device (using TestFlight) and it worked as expected and just like a development build. This was with build 2576.

#8

Thanks, Tom. Yes, I’m able to upload the distribution build to apple and they reviewed it. But the app did not work as expected on their devices, while during our tests on the ad-hoc version it worked well. Also, the app is based on code that close to 100% similar to previous apps we uploaded just weeks ago using build 2511 with no such issues.

I agree the problem may be unrelated to the build, but it manifest itself on these builds. 

#9

You could upload a distribution build for testing using Apple’s TestFlight and then download that version to your device and see what’s going on.  There are very few things that are different between an AdHoc build and an Distribution build, mostly involving sandboxes for GameCenter, IAP and Push Notifications.

Rob

#10

Yes, we tried that and the problem does not reproduce on our devices when using test flight. I really don’t know what to do now. something changed and I do not have the tools to debug it.

#11

You should have never been permitted to use a release profile directly installed.  Developer and Release/AdHoc are the only two that can be put on a test device, unless you’re using Apple’s new TestFlight, which actually uses the Release/Store profile.

rob

#12

That’s not true Rob. Perhaps they did not intend to have that, but once you have a dev or an ad-hoc profile on your device, you can install a release version of that app on a test device. what troubles me is that we were able to verify that the release build is running properly on our test devices before and now we can’t. 

#13

My two latest apps have been rejected by apple due to bugs in game play. This is for a code that used to work in previous apps with no issues. When testing using the ad-hoc certificate everything seems fine. The problem remains that I can test on my device the distribution version as I used to.

I don’t know what you did to the build process for the release version but the problem seem to originate from there. 

#14

Seems I’m not the only one who found this issue. There are many comments on that here:

http://coronalabs.com/blog/2015/01/21/update-on-corona-ios-64-bit-support-and-plugins/#comment-503573

I suspect it also causes the problem we currently see in approving our app in apple review process.

We narrowed the problematic build down. The code we are trying to submit works flawlessly on build 2525, but fails for some reason starting from build 2526.

You have made some breaking change during build 2526, probably as part of making this fix:

  • Mac - Fix issues with building for TestFlight (beta-reports-active) and duplicate codesigning identities - casenums 37100, 37124

Please look into it. If you need me to provide the binaries to show the different behavior I can be reached at

info@tiltangames.com

www.tiltangames.com

Adi

#15

I have never been able to run a distribution app (non Ad-hoc) on a test device. I just did a build with 2576 and 2511 with a Store Distribution provisioning profile and both fail to install on an iPad iOS 8.1 device. I have both a developer profile and adhoc profile on the device.

I Googled the issue and found a Stack Overflow thread saying this worked at one time but is not longer the case:

This seems not to be the case anymore - e.g. AppStore provisioning profiles signed builds won’t install on devices with AdHoc provisioning profiles anymore. –  DotNetWise Feb 10 at 11:22

This answer is showing its age - it needs to be updated. The old behaviour may have been a bug… There’s always re-signing your app store builds to get the final build on a device. –  Rhythmic Fistman Feb 12 at 0:30

http://stackoverflow.com/questions/21019760/how-come-i-can-install-an-app-store-distribution-build-directly-on-my-device

#16

I just built our Fishes and MuitiPuck sample apps with App Store Distribution and uploaded them to iTunesConnect. I tested the apps on an iOS 8.1 device (using TestFlight) and it worked as expected and just like a development build. This was with build 2576.

#17

Thanks, Tom. Yes, I’m able to upload the distribution build to apple and they reviewed it. But the app did not work as expected on their devices, while during our tests on the ad-hoc version it worked well. Also, the app is based on code that close to 100% similar to previous apps we uploaded just weeks ago using build 2511 with no such issues.

I agree the problem may be unrelated to the build, but it manifest itself on these builds. 

#18

You could upload a distribution build for testing using Apple’s TestFlight and then download that version to your device and see what’s going on.  There are very few things that are different between an AdHoc build and an Distribution build, mostly involving sandboxes for GameCenter, IAP and Push Notifications.

Rob

#19

Yes, we tried that and the problem does not reproduce on our devices when using test flight. I really don’t know what to do now. something changed and I do not have the tools to debug it.