Looking at the code I see that the 6.0 value is only set if
ios.bitcode=true and it defaults to false.
That last error is exactly why we reverted the iphone_new change and
returned to the older build servers. We are working on a major overhaul to
the build process to circumvent that error. Hope
another iphone build failed right after a successful build
ProcessProductPackaging /Users/administrator/Library/MobileDevice/Provisioning\
Profiles/TempProfile.mobileprovision
build/Release-iphoneos/[REDACTED].app/embedded.mobileprovision
cd
/var/folders/zh/kb_4hqhn4kg1h0r5dp_6htcmgn/T/
the latest iphone build was successful, the Info.plist file looks like below
{
"CFBundleName" => "[REDACTED]"
"DTSDKName" => "iphoneos9.3"
"DTXcode" => "0731"
"CFBundleIcons~ipad" => {
"CFBundlePrimaryIcon" => {
"CFBundleIconFiles" => [
0 => "AppIcon29x29"
1 => "A
Hi Shai, last four requests at minimum were for distribution build. Not
only that, I changed the build target to use "iphone_new" for the following
ant tasks. The last successful iPhone release build from CN1 still has
CFBundleInfoDictionaryVersion as 5.1.1.
build-for-ios-device
build-for-io
Distribution builds != Development builds and you seem to send both. If you
made your own certificates/provisioning then there are MANY reasons these
can fail:
http://www.codenameone.com/blog/ios-code-signing-fail-checklist.html
You seem to be sending builds to iphone and not to iphone_new whic
iPhone build failed for the fourth time
** BUILD SUCCEEDED **
Skipping application-groups entitlement
Exception: java.io.FileNotFoundException:
/Users/administrator/Library/MobileDevice/Provisioning
Profiles/TempProfile.mobileprovision (No such file or directory)
java.io.FileInputStream.open0(N
Android build was a success
On Monday, June 20, 2016 at 4:50:49 PM UTC-4, DVR Alarm wrote:
>
> our corporate Airwatch MDM solution is throwing the following error during
> app-wrapping when deploying the iOS version of the application. The
> android version is working. Upon research with the I
third build failed with the following error (TOTALLY) different from last
two failed builds. I am going to build for Android now to see what happens:
ProcessProductPackaging /Users/administrator/Library/MobileDevice/Provisioning\
Profiles/TempProfile.mobileprovision
build/Release-iphoneos/[RED
I need to hear a GOOD explanation of the differences. Between my last two
builds sent to CN1 build server nothing changed in my code, certificate,
profile or build configuration. Although the latest build failed like the
earlier build, but messages are completely different between last two
bui
another build sent to CN1 builder server for iphone returned with error as
below, I am going to send another build to CN1 build server to if I get
the same error back:
** BUILD SUCCEEDED **
Skipping application-groups entitlement
codesign -f -vv --entitlements
/var/folders/zh/kb_4hqhn4kg1h0r5
automagically the iphone build is working again, but the original issue of
CFBundleInfoDictionaryVersion being 5.1.1 is still the same
On Monday, June 20, 2016 at 4:50:49 PM UTC-4, DVR Alarm wrote:
>
> our corporate Airwatch MDM solution is throwing the following error during
> app-wrapping when
modified the build.xml and got the following error on CN1 build server
** BUILD SUCCEEDED **
Skipping application-groups entitlement
Exception: java.io.FileNotFoundException:
/Users/administrator/Library/MobileDevice/Provisioning
Profiles/TempProfile.mobileprovision (No such file or directory)
Our new xcode build servers use 6.0 so they should work. You can follow our
process of migrating to them in the blog.
To use them use the iphone_new target as explained here:
https://www.codenameone.com/blog/ios-server-migration-plan.html
https://www.codenameone.com/blog/ios-migration-continued.h
13 matches
Mail list logo
