June 25 release breaks iOS developer deploy

[Robert]

It appears that the June 25th release has broken the ability for either Graphite or Mist to run (deploy) on iOS using a development profile.  We have confirmed this problem on 2 or 3 developer machines and 2 (or more) iPads.  Prior to the June 25th release, we were able to deploy and run on our test devices without issue; after the update, we cannot redeploy -- Icenium insists that the device in question is not included in the provisioning profile.

As the person responsible for the provisioning profile (and an iOS developer have several year), I am 100% confident that the devices are included in the provisioning profile; nevertheless, I re-checked the profile and verified that the devices are included.  The profile expires in May of 2014, so expired profiles can be ruled out.

This is a huge problem and needs to be resolved urgently.

As an addendum, I have figured out that I can get this working again by deleting any additional profiles from Graphite or Mist.  It appears that Graphite and Mist are showing one profile as being selected yet are using the wrong profile when building.

[Todd Heemsoth]

As reported by Robert, we also are experiencing that the June 25th release has broken the ability for either Graphite or Mist to run (deploy) on iOS. In addition, the simulator has stopped working and continuously shows blue spinner and 'Loading..' message.

Please advise as we are needing to submit our app to the Apple App Store this week.

[Ivan Ivanov]

Hi,

We tried everything possible but couldn't reproduce the issue you encountered. Can you give us more information?

You could send us build logs from output pane or if you like, you can record your actions in a video (like screencast.com) and share it so I can see exactly what happens.

Sorry for any inconvenience caused.

Regards,
Ivan Ivanov
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Missed our first webinar, watch it here.
Share feedback and vote for features on our Feedback Portal.

[Ivan Ivanov]

Hello Todd,

After we investigated your issue we found out that the .proj file has been modified after the addition of a certain file. After that this file has been reverted but the changes in the .proj file remained. This led to the project being loaded wrong. We've fixed the .proj file and hopefully all will be alright. We are also thinking about how to prevent similar project file related issues in the future.

Sorry for the inconvenience. If you encounter any other issues don't hesitate to contact us again.

Regards,
Ivan Ivanov
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Missed our first webinar, watch it here.
Share feedback and vote for features on our Feedback Portal.

[Robert]

[quote]

"After we investigated your issue we found out that the .proj file has been modified after the addition of a certain file."
[/quote]

Would this be indicative of a problem in our .proj file as well, and how would we go about resolving it?

[Ivan Ivanov]

Hello Robert,

We are still investigating your issue. As requested earlier, we would appreciate any videos that provide us with steps to reproduce and/or additional information that might help us in investigating your issue further.

Thank you in advance.

Regards,
Ivan Ivanov
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Missed our first webinar, watch it here.
Share feedback and vote for features on our Feedback Portal.