- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using Intel XDK build 1878 on Mac OS X Yosemite. Android build works fine and I get an email with the .apk, but the iOS build fails with the messages below. There is no way that I can see to view any further details to determine why the build is failing. Help would be appreciated as I can only take a wild guess at what is wrong.
Thanks, Eldon
- Building a Cordova 3.5 application.
- The application name is "InnoVision Medical"
- The package name is "com.innovisionmedical.innovisionapp"
- Will use the provisioning profile for "production"
- Plugin "org.apache.cordova.device" (0.2.9) installed.
- Targeting iOS version 5.1.1.
- Copied 120.png (120x120) image file to icon-60@2x
- Copied 152.png (152x152) image file to icon-76@2
- Copied 76.png (76x76) image file to icon-76
- Copied 60.png (60x60) image file to icon-60
- Copied 180.png (180x180) image file to icon-60@3x
- Copied the iPad portrait [768x1004.png] (768w x 1004h) splash screen to Default-Portrait~ipad.
- Copied the iPhone 6 Landscape [1334x750.png] (1334w x 750h) splash screen to Default-Landscape-667h@2x.
- Copied the iPhone 6 Plus Landscape [2208x1242.png] (2208w x 1242h) splash screen to Default-Landscape-736h@3x.
- Copied the iPad Retina Landscape [2048x1496.png] (2048w x 1496h) splash screen to Default-Landscape@2x~ipad.
- Copied the iPad Landscape [1024x748.png] (1024w x 748h) splash screen to Default-Landscape~ipad.
- Copied the iPhone 6 Plus Portrait [1242x2208.png] (1242w x 2208h) splash screen to Default-736h@3x.
- Copied the iPhone 5 [640x1136.png] (640w x 1136h) splash screen to Default-568h@2x~iphone.
- Copied the iPhone Retina [640x960.png] (640w x 960h) splash screen to Default@2x~iphone.
- Copied the iPhone [320x480.png] (320w x 480h) splash screen to Default~iphone.
- Copied the iPad Retina portrait [1536x2008.png] (1536w x 2008h) splash screen to Default-Portrait@2x~ipad.
- Copied the iPhone 6 Portrait [750x1334.png] (750w x 1334h) splash screen to Default-667h@2x.
- Tags:
- HTML5
- Intel® XDK
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here, since yesterday afternoon the detailed build log seems te be gone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The detailed build logs are still there. There are some build errors the cause these logs to not be generated though.
Also, it could have been a server hiccup. Can you try your build again and let me know if it worked?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks John! I just retried the build (7:40am PDT) and got what looked like the exact same results on the "The build failed." page with no link to any detailed results. I neglected to mention in my original post that it happens repeatedly, so I don't think it is a server hiccup. Is there any other way to get access to the detailed logs when this happens?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like your provisioning profile does not match the certificate that you have uploaded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Everything looks good to me in the apple developer portal. Which provisioning file doesn't match the certificate and is there filenames you can see that I uploaded on the build server (ios_distribution-10.cer) with a User ID of 93676MK875? The cert should expire March 29, 2016 and I see it listed in the details on both the app store and ad hoc distribution profiles which I attached to the project as AppStore.mobileprovision and AdHoc.mobileprovision respectively before building. What cert is showing up in the .provision files on the build server, what is the expiration date and or the user id or is something else not matching?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the public key for the cert used in both provisioning files.
B4 73 84 E5 A7 37 69 0A E6 A3 39 A4 89 77 55 0F 15 76 E3 9F C1 29 D0 0C 19 86 DC 50 3E A2 FD 18 C1 58 D0 96 85 14 9C C7 F3 91 F1 19 8F 7B 2C 43 36 36 3A FA A0 63 21 4C 3D 5A 36 EC ED 5B C4 26 52 E9 9A 2F CC 5E 40 BF 39 66 51 6C 84 48 F4 6D F4 C6 26 DF 4D CA 38 9D AF 9D D2 8E C6 0F D5 AF 51 FE 6F 17 CC 52 7E 80 4F E0 0D 67 B1 2E 71 D0 DF 2C BF E0 1F 79 18 CA C9 7F 03 B7 58 65 8C D2 91 66 AF 4F 9A 54 65 85 E0 9A 4E F7 5B 49 E2 2D A0 36 0A 9F 35 36 80 FF B2 CC B1 99 20 C4 46 F9 B3 B8 A7 86 D6 8B B1 26 77 0B B0 FB D1 80 97 CC 6E 85 40 89 DF 9A E2 E3 02 CE 83 20 24 01 7F 1D 65 FF 1B 69 7E 2B 96 9D 9B 5E C9 EA A9 7F 47 2E C9 DE 97 93 73 42 94 F2 CF F7 FD CC 52 E1 EA 08 21 1E CF 44 13 63 29 0B 4F DC 4F 98 10 F9 39 74 B0 5F 25 C2 DC 96 D3 BE BE CB AA 69 DF 79 3C 9B
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
John, I'm interested in resolving this certificate mismatch issue as I don't understand why it is happening, but back to the original request of build log details, would there be a way to improve the build process so a XDK user wouldn't have to post and have you look into this to get to understanding and resolution of the problem? Could logic be added that detects that the cert and provisioning files have a mismatch and alert the user at the beginning of the process on the mismatch details?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That I can not tell. I can see you have multiple .cer files in your bundle, which means to me that you have been playing around trying to get something to work. :)
Try following this guide. Once you have your Distribution cert setup, you will need to reissue your provisioning profile, download it, and give it to the XDK in the settings. Also, make sure you have your AppID set up correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've done exactly what that guide suggests (to the best of my knowledge) repeatedly. Everything looks to match up to me, the only thing I can think of is something is not right on the build server when I upload the new .cer or reference new .mobileprovision files, but I have no idea what it could be as I don't have a detailed build log. Is it possible that the build server is not accepting the cert I'm uploading to it for some reason? How can I better debug this other than revoking and regenerating over and over just to have the same thing occur. As for the App ID, I see on the provisioning profile editor the name followed by parentheses with (93676MK875.com.innovisionmedical.innovisionapp). In my XDK project, I have a App ID set to com.innovisionmedical.innovisionapp. I see on this forum there have been others that have had a similar problem and you were able to get access to their apple developer login info and fix things. Seems like something in the build process that the XDK user needs more visibility on!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you add the 93676MK875 to the AppID in the XDK? You should not. Enter exactly what you entered for the apple developer portal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, I entered com.innovisionmedical.innovisionapp in the XDK for App ID. This seems to show up in the build log that I referenced in my OP. I've included it below with the line in bold. Note, I tried building with the production and ad-hoc profiles and both fail the same way with no link to any detailed log.
The build failed.
An error occurred while building the application. Verify your build assets are correct and try again.
Build Log:
- Building a Cordova 3.5 application.
- The application name is "InnoVision Medical"
- The package name is "com.innovisionmedical.innovisionapp"
- Will use the provisioning profile for "production"
- Plugin "org.apache.cordova.device" (0.2.9) installed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I cant really tell you anything else. If you want me to log into your account in the morning and set things up for you, let me know. I will need your apple developer account and xdk account logins. Send me a private message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So after working with John directly for a few days we found out that it is a problem with App Name in your project settings for the iOS build. I don't have the full details from them on what the limitation is but was told it is a bug and that may be dealt with at some time (but no promises). The best workaround for now is to keep the App Name value in the build settings to be the same exact name as the XDK project name or to name it something completely different. Definitely don't enter a value for "App Name" that starts with the project name, that will result in this behavior every time.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page