Hi!
I just created a new app and tried to test it on my iphone. So I uploaded it through itunes and it appeared on my iphone. However I was not able to open the app, it was stuck on “installing…”. Has this happened to anyone? Any ideas?
thanks in advance!
Have you created a proper ad hoc profile? check this article http://docs.coronalabs.com/guide/distribution/iOSBuild/#distribution-ad-hoc
It’s easier to use xCode organizer for testingas for me
Are there any messages in your device’s console log? If you don’t know how to look at it, read this tutorial:
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Have you created a proper ad hoc profile? check this article http://docs.coronalabs.com/guide/distribution/iOSBuild/#distribution-ad-hoc
It’s easier to use xCode organizer for testingas for me
Are there any messages in your device’s console log? If you don’t know how to look at it, read this tutorial:
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Hi,
same here. App would be installed on device properly, once launched it just displays ‘installing’ again, under the icon, and remains stuck there…
Tried the debugging process — errors returned:
o:setTextColor() is deprecated. Use o:setFillColor() instead
Would this be enough to cause such a problem??
---------------------- UPDATE :
I changed the method setTextColor to setFillColor, and the debugger now returns
‘attempt to call method setFillColor - a nil value’
while simulating.
How am I gonna fix this???
---------------------- UPDATE :
If I install the app on the device with xcode - drag and drop - instead of itunes I get:
‘The application does not have a valid signature’
from xcode.
I tried performing the whole process illustrated here: http://docs.coronalabs.com/guide/distribution/iOSBuild/index.htmltwice with both developing and ad hoc provisions.
The only thing I did differently from the forementioned set of instruction was to load the provisioning files on the device through Xcode instead that from Itunes.
Any idea about what’s possibly going on here???
---------------------- UPDATE :
now I also tried loading the provisioning files on device through itunes syncing. Same del as before:
‘The application does not have a valid signature’. If I load the app with xcode
The whole restarts installing and gets stuck there thing, if l load it with itunes.
What’s going on here? Anyone could help?? At least could someone redirect me on how to clean previous provisions and start the process again from a clean slate??
Thank a lot!!
so I guess third time’s a charm.
I deleted previous certificates and provisions and repeated the whole process again, this time it did for me.
For anyone interested, I could not discern any truly effective trick to solve the issue. I did everything exactly the same except not using itunes at all. I left it out of the process by uploading provision and app through xcode.
That did the trick for me, but I can’t swear that’s been the agent of success… I would suggest, as many other reported, to focus on ‘cleaning’ old certificates-provisions and start the build from scratch.
I am having the same issue NOW !! It was working fine and now I am getting the same message as you did The Application does not have a valid signature !! Does not make any sense. Getting aggravated !!! There should not be a need to delete the Provisioning Profiles if they are valid !!
There must be a fix for this will continue to search and try my own process of elimination.
JZ
Yeah, I’d suggest to go over the process again while considering what you did different from before the emergence of the issue and keeping an eye on provisionings’ expiry dates and such. It’s an articulate kind of process apple has imposed so every tiny misstep can possibly be crucial and lead to the insurgence of errors and malfunctioning…
Hi,
same here. App would be installed on device properly, once launched it just displays ‘installing’ again, under the icon, and remains stuck there…
Tried the debugging process — errors returned:
o:setTextColor() is deprecated. Use o:setFillColor() instead
Would this be enough to cause such a problem??
---------------------- UPDATE :
I changed the method setTextColor to setFillColor, and the debugger now returns
‘attempt to call method setFillColor - a nil value’
while simulating.
How am I gonna fix this???
---------------------- UPDATE :
If I install the app on the device with xcode - drag and drop - instead of itunes I get:
‘The application does not have a valid signature’
from xcode.
I tried performing the whole process illustrated here: http://docs.coronalabs.com/guide/distribution/iOSBuild/index.htmltwice with both developing and ad hoc provisions.
The only thing I did differently from the forementioned set of instruction was to load the provisioning files on the device through Xcode instead that from Itunes.
Any idea about what’s possibly going on here???
---------------------- UPDATE :
now I also tried loading the provisioning files on device through itunes syncing. Same del as before:
‘The application does not have a valid signature’. If I load the app with xcode
The whole restarts installing and gets stuck there thing, if l load it with itunes.
What’s going on here? Anyone could help?? At least could someone redirect me on how to clean previous provisions and start the process again from a clean slate??
Thank a lot!!
so I guess third time’s a charm.
I deleted previous certificates and provisions and repeated the whole process again, this time it did for me.
For anyone interested, I could not discern any truly effective trick to solve the issue. I did everything exactly the same except not using itunes at all. I left it out of the process by uploading provision and app through xcode.
That did the trick for me, but I can’t swear that’s been the agent of success… I would suggest, as many other reported, to focus on ‘cleaning’ old certificates-provisions and start the build from scratch.
I am having the same issue NOW !! It was working fine and now I am getting the same message as you did The Application does not have a valid signature !! Does not make any sense. Getting aggravated !!! There should not be a need to delete the Provisioning Profiles if they are valid !!
There must be a fix for this will continue to search and try my own process of elimination.
JZ
Yeah, I’d suggest to go over the process again while considering what you did different from before the emergence of the issue and keeping an eye on provisionings’ expiry dates and such. It’s an articulate kind of process apple has imposed so every tiny misstep can possibly be crucial and lead to the insurgence of errors and malfunctioning…