[will]

Hi ive been using mobi one for a while now and have successful developed both an ad hoc distributed native app and an app store version. For the ad hoc version ive been able to install it before happily but now it simply states “cannot be installed at this time” ive checked my provisioning profiles and UDID keys and they are all correct.
Oddly when installed directly by hand it appears to work leading me to believe i’ve made an error using the cloud service somehow.

Could you please suggest some possible issues for me to investigate as i am not an IT specialist and am at a bit of a loss at the moment.

Build Number: 354717

Thanks

[NigelShaw]

Hi,

i may be wrong but im sure the Ad-Hoc & generally the Dev certificates have a short lifespan. They are not indefinate.

Thanks

Nigel

[will]

thanks Nigel ill look into this

[will]

Tried Changing Certificates, Names, rebuilding. Please Can someone help app still just installs almost all the way and then says “could not be installed at this time” at a loss as to how to proceed.

[support-octavio]

Hi will,

Dev team has reviewed your build ID, and didn’t found anything odd. It seems that you didn’t added your device to the provisioning profile. The advice is to recreate your provisioning profile file to be sure that you’ve added your current device on it. Let us know how it goes.

[will]

Thanks for the reply think ive sorted it now.

Basically although i upload a new provisioning profile mobi one was still using the old one so had to delete all the old certificates and profiles and create a new ones so mobi one recognised a change and uploaded the new ones. I think changeing so mobi one re-uploads the certificate each time would be useful as this problem was very frustrating and had me confused for ages (maybe i was just being thick 🙂 ).

[support-octavio]

@will,

Thanks for sharing your success. Glad you have your app working now. Closing thread.

[Author]

Posts