This question is locked. New answers and comments are not allowed.
All,
I am having trouble building any type of iOS release for my phone that requires certificates. I have done the following:
1) Requested a csr from Icenium Mist
2) Saved the csr file locally.
3) Created a new AdHoc cert on the Apple Dev Site using the csr
4) Saved the AdHoc cer file locally.
5) Created a new AdHoc mobile provisioning profile on the Apple Dev Site using the AdHoc cer file
6) Saved the mobileprovision file locally
7) Completed the Mist CSR by uploading the cer file
8) Imported the mobileprovision file
Once this is all complete, I see I have my AdHoc provisioning profile and my cert in Mist
1) I select Run->Build
2) I select iOS Build with Provision
3) The correct AdHoc mobileprovision is selected and the associated cert is attached, however, the cert has an expiration of 8/21/2014 yet shows an expired cert alert
4) The build succeeds
5) I cannot download the build using the QR code (unable to install error message) or manually (page not found error)
6) When I return to the certificates page in MIST, my mobileprovision is present, but my cert disappears. Closing the project and reopening it seems to refresh everything.
Can someone please confirm this as a bug of epic proportion or provide me with clear instructions and guidance as to where I exited the reservation? I am going nuts with this. I really want to test a background plugin and can only do so with a provisioned build.
Thanks,
Bruce
I am having trouble building any type of iOS release for my phone that requires certificates. I have done the following:
1) Requested a csr from Icenium Mist
2) Saved the csr file locally.
3) Created a new AdHoc cert on the Apple Dev Site using the csr
4) Saved the AdHoc cer file locally.
5) Created a new AdHoc mobile provisioning profile on the Apple Dev Site using the AdHoc cer file
6) Saved the mobileprovision file locally
7) Completed the Mist CSR by uploading the cer file
8) Imported the mobileprovision file
Once this is all complete, I see I have my AdHoc provisioning profile and my cert in Mist
1) I select Run->Build
2) I select iOS Build with Provision
3) The correct AdHoc mobileprovision is selected and the associated cert is attached, however, the cert has an expiration of 8/21/2014 yet shows an expired cert alert
4) The build succeeds
5) I cannot download the build using the QR code (unable to install error message) or manually (page not found error)
6) When I return to the certificates page in MIST, my mobileprovision is present, but my cert disappears. Closing the project and reopening it seems to refresh everything.
Can someone please confirm this as a bug of epic proportion or provide me with clear instructions and guidance as to where I exited the reservation? I am going nuts with this. I really want to test a background plugin and can only do so with a provisioned build.
Thanks,
Bruce
9 Answers, 1 is accepted
0
HJ
Top achievements
Rank 1
Rank 1
answered on 25 Aug 2013, 05:06 AM
Not that it is any consolation... but I am HAVING THE SAME PROBLEM !!!...
In my case HOWEVER, a bit worse...
I have been "sucessfully" building the IPA file for (test) release for several months (with given Cert + Provisioning files);
THEN I decided to create a NEW ADHOC PROVISIONING FILE, using same (previous) Certificate...
and when using this newly created provision, it SAYS it IS EXPIRED (8/24/2013)...
but My APPLE Developer site says it is valid thru FEB, 2014 !!!...
I sure would like to know WHAT's GOING ON ... I am sure everything has an explanation...
but have not found any answers that HELP SOLVE this problem (or even identify it with more details/cause).
HELP... HELP... HELP
In my case HOWEVER, a bit worse...
I have been "sucessfully" building the IPA file for (test) release for several months (with given Cert + Provisioning files);
THEN I decided to create a NEW ADHOC PROVISIONING FILE, using same (previous) Certificate...
and when using this newly created provision, it SAYS it IS EXPIRED (8/24/2013)...
but My APPLE Developer site says it is valid thru FEB, 2014 !!!...
I sure would like to know WHAT's GOING ON ... I am sure everything has an explanation...
but have not found any answers that HELP SOLVE this problem (or even identify it with more details/cause).
HELP... HELP... HELP
0
Accepted
Hi guys,
@Bruce: The expired sign is a bug in Mist as the certificate is clearly valid (indicated by its expiration date). It would be fixed for subsequent version of Icenium and you can ignore it till then. If the QR code has been generated it means the build is successful, the fact that it contains an URL confirms that. Most likely your QR code reader can't recognize the code as a hyperlink and that is why you get an erorr. Feel free to try with another reader, such as RedLaser or QRReader. You could also use the Download link to download the .ipa and install the app manually via iTunes.
@HJ: I think you're hitting the Mist bug of showing expired warning sign as well. I've checked your provision and it shows valid date on my end 8/25/2014, so if you're not having any problems building, please ignore the expired warning as well. If your problem differs, please elaborate as we do not see any problem with your provision/certificates.
Regards,
Steve
Telerik
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
@Bruce: The expired sign is a bug in Mist as the certificate is clearly valid (indicated by its expiration date). It would be fixed for subsequent version of Icenium and you can ignore it till then. If the QR code has been generated it means the build is successful, the fact that it contains an URL confirms that. Most likely your QR code reader can't recognize the code as a hyperlink and that is why you get an erorr. Feel free to try with another reader, such as RedLaser or QRReader. You could also use the Download link to download the .ipa and install the app manually via iTunes.
@HJ: I think you're hitting the Mist bug of showing expired warning sign as well. I've checked your provision and it shows valid date on my end 8/25/2014, so if you're not having any problems building, please ignore the expired warning as well. If your problem differs, please elaborate as we do not see any problem with your provision/certificates.
Regards,
Steve
Telerik
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
Bruce
Top achievements
Rank 1
Rank 1
answered on 27 Aug 2013, 02:15 PM
Hi Steve,
That is kind of what I thought...As for the original issue, I think something got munched in my GeoAPITestApp project. I created GeoAPITestApp2 and everything seems to be hooked up correctly except for the plugins, which is a different issue altogether and is posted elsewhere.
Thanks,
Bruce
That is kind of what I thought...As for the original issue, I think something got munched in my GeoAPITestApp project. I created GeoAPITestApp2 and everything seems to be hooked up correctly except for the plugins, which is a different issue altogether and is posted elsewhere.
Thanks,
Bruce
0
Hi Bruce,
I was able to build and install your GeoAPITestApp project locally without any issues, so I cannot confirm whether there is a problem specific to it.
Regards,
Steve
Telerik
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
I was able to build and install your GeoAPITestApp project locally without any issues, so I cannot confirm whether there is a problem specific to it.
Regards,
Steve
Telerik
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
HJ
Top achievements
Rank 1
Rank 1
answered on 27 Aug 2013, 06:44 PM
Hi Steve... Thanks very much for your prompt responses.
Here is yet another ( "bug" ? ) instance where BUILDING an iOS release just failed under GRAPHITE...
Following these steps...
1) ... Created CSR file in Icenium GRAPHITE
... THEN used that file to generate a PRODUCTION Certificate at Apple's Developer site... ( *.cer File)
... and corresponding MOBILE PROVISIONING file for DISTRIBUTION on APPLE's iTunes store
2) IMPORTED both files into Icenium
3) Attemped to "Build iOS release" using "distribution provisioning File"...
... but ICENIUM refuse to build, saying "No Provisioning File FOUND" ???...
*** HOWEVER, I can BUILD OK when using an ADHOC Provisioning *** with an specific "BUNDLE ID"
THE QUESTIONS ARE ?...
- Given fact that there are NO DEVICES in the "distribution" provisioning file, IS THIS SUPPORTED ???...
- IF this was supported in the past (which I do not know), DID APPLE CHANGE anything ???...
- My Provisioning File was generated using BUNDLE ID like: "com.domain.*"... IS THIS SUPPORTED ?...
I Can send/eMAIL all related files for your inspection if you provide eMail address
Thanks again
Here is yet another ( "bug" ? ) instance where BUILDING an iOS release just failed under GRAPHITE...
Following these steps...
1) ... Created CSR file in Icenium GRAPHITE
... THEN used that file to generate a PRODUCTION Certificate at Apple's Developer site... ( *.cer File)
... and corresponding MOBILE PROVISIONING file for DISTRIBUTION on APPLE's iTunes store
2) IMPORTED both files into Icenium
3) Attemped to "Build iOS release" using "distribution provisioning File"...
... but ICENIUM refuse to build, saying "No Provisioning File FOUND" ???...
*** HOWEVER, I can BUILD OK when using an ADHOC Provisioning *** with an specific "BUNDLE ID"
THE QUESTIONS ARE ?...
- Given fact that there are NO DEVICES in the "distribution" provisioning file, IS THIS SUPPORTED ???...
- IF this was supported in the past (which I do not know), DID APPLE CHANGE anything ???...
- My Provisioning File was generated using BUNDLE ID like: "com.domain.*"... IS THIS SUPPORTED ?...
I Can send/eMAIL all related files for your inspection if you provide eMail address
Thanks again
0
Hi HJ,
This is not a bug. Whenever you want to build your app for the App Store, you should use the Publish option in Graphite. The Built option should be used only for ad-hoc/development (see Publish to App Store (iOS)). To answer your questions directly:
Steve
Telerik
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
This is not a bug. Whenever you want to build your app for the App Store, you should use the Publish option in Graphite. The Built option should be used only for ad-hoc/development (see Publish to App Store (iOS)). To answer your questions directly:
- In the Apple App Store you can publish only apps created with an App Store distribution provisioning profile. Compared to ad-hoc/developer profile, you are not required to register any devices.
- No changes were made on this front by Apple.
- If the App ID is a wildcard App ID, the application identifier must comply with the format of the bundle identifier. For example, if your wildcard bundle identifier is
com.<company_name>.*, a valid application identifier will becom.<company_name>.<app_name>. Using wildcard bundle identifier is not really recommended for distribution, as you would not be able to use services like Push Notifications, In-App Purchase, Game Center, and so on.
We would like to note that all this information is part of the Apple docs and not directly related to Icenium, so if you plan to publish an App to the AppStore, it is recommended to get familiar with the instructions and requirements to do so.
Regards,Steve
Telerik
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
HJ
Top achievements
Rank 1
Rank 1
answered on 30 Aug 2013, 06:02 PM
Steve...
READ your recommended LINKS (at APPLE's website)...
Thanks for effectively and accurately pointing that out.
Corollary:
*** shouldv'e done my homework ***
READ your recommended LINKS (at APPLE's website)...
Thanks for effectively and accurately pointing that out.
Corollary:
*** shouldv'e done my homework ***
0
Bruce
Top achievements
Rank 1
Rank 1
answered on 31 Aug 2013, 01:03 PM
Steve,
This was never really resolved. As a workaround I created a new project and added all new certs and for a while this worked, but it just reared its ugly head again today with my GeoAPITestApp2 project.
Everything was going well. I had rebuilt all my dev and push ssl certs and mobile provisions and everthing imported as expected. My ADHOC and DEV provisions correctly showed my ADHOC and DEV certs. When I tried to run the app the last time, however, I got a push error about APS-ENVIRONMENT not being defined. After research, I found I needed to delete my mobile provisions and recreate them. I did this on Apple, downloaded them, and imported them into Icenium. When I went to rebuild at this point, I can no longer install on the device. Regardless of whether I user RedLaser to get the app or just download the IPA file, I get a file not found message or unable to download message.
As a test, I cloned the sample Everlive Push App as a new project. I assigned the project the org.jaxmeier.geoapitestapp2 bundle so it would use the same certs and provisions as my GeoAPITestApp2 app. Everything built and got on the device with no issues whatsoever.
This leads me to believe there might be something going on with the application's ability to release and reapply certificates or mobile provisions, not really an issue with the certs and provisions themselves.
I really don't want to have to continue to copy and recreate projects whenever this happens. Are there any error logs or messages on the Icenium side that might point to this issue?
Thanks,
Bruce
This was never really resolved. As a workaround I created a new project and added all new certs and for a while this worked, but it just reared its ugly head again today with my GeoAPITestApp2 project.
Everything was going well. I had rebuilt all my dev and push ssl certs and mobile provisions and everthing imported as expected. My ADHOC and DEV provisions correctly showed my ADHOC and DEV certs. When I tried to run the app the last time, however, I got a push error about APS-ENVIRONMENT not being defined. After research, I found I needed to delete my mobile provisions and recreate them. I did this on Apple, downloaded them, and imported them into Icenium. When I went to rebuild at this point, I can no longer install on the device. Regardless of whether I user RedLaser to get the app or just download the IPA file, I get a file not found message or unable to download message.
As a test, I cloned the sample Everlive Push App as a new project. I assigned the project the org.jaxmeier.geoapitestapp2 bundle so it would use the same certs and provisions as my GeoAPITestApp2 app. Everything built and got on the device with no issues whatsoever.
This leads me to believe there might be something going on with the application's ability to release and reapply certificates or mobile provisions, not really an issue with the certs and provisions themselves.
I really don't want to have to continue to copy and recreate projects whenever this happens. Are there any error logs or messages on the Icenium side that might point to this issue?
Thanks,
Bruce
0
Accepted
Bruce
Top achievements
Rank 1
Rank 1
answered on 31 Aug 2013, 02:54 PM
*** UPDATE ***
I tried using Graphite to determine if it would show me more build errors than Mist did. It did, and here is what I found out. Somehow the js, h, and m files in my PushPlugin plugin were mysterously replaced with HTML. I have no idea how, but they were. Once I replaced them with their proper content, it built.
Mist gave me no indication this had happened and displayed no build errors whatsoever (a bit problematic!) but fortunately I have a Windows box that I could install Graphite on.
Bruce
I tried using Graphite to determine if it would show me more build errors than Mist did. It did, and here is what I found out. Somehow the js, h, and m files in my PushPlugin plugin were mysterously replaced with HTML. I have no idea how, but they were. Once I replaced them with their proper content, it built.
Mist gave me no indication this had happened and displayed no build errors whatsoever (a bit problematic!) but fortunately I have a Windows box that I could install Graphite on.
Bruce