Just trying live build for first time on IOS. Using 997 on the Mac.
Image attached… The same app built successfully without live build.
Conor,
What is 997? I think you’re looking at the wrong number. (Unless of course you mean 2016.2 997?)
Version numbers come in this format 2016.XXXX
Take a peek at your simulator when you first start it (see image) and you should see the version you’re using.
Thanks,
Ed
Sorry, it’s 2997, typo. Latest.
All good, just wanted to be sure.
Is there more information in the console log from the build?
Rob
This is the information from the console
Dec 06 07:45:40.036 Building ios app for conor@…com with 2016.2997
Dec 06 07:45:42.374 Using custom build id from app bundle: 00000 (AppSettings.lua)
Dec 06 07:45:42.705 BUILD ERROR: /var/folders/1x/8glztypj1fn_7_qk2dnv0fcm0000kr/T/CLtmpYr2u4f/main.lua:1: unfinished string near '‘6153def9-64a2-4335-a4c6-e5c09a7dbee6’
Dec 06 07:45:42.724 iOS build failed (5) after 0 seconds
Dec 06 07:45:43.120 ERROR: Build Failed: Error code: 5
Dec 06 07:45:43.120
Please note, the build executes properly if livebuild is not selected.
System is macincloud osx El Capitan 10.11.6
In case it’s relevant here are my plugins
plugins = { ["plugin.OneSignal"] = { publisherId = "com.onesignal", }, ["plugin.google.play.services"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true, ["android-kindle"]=true }, }, },Could you please PM me contents of .CoronaLiveBuild file you have in your project root? It seems that “key” property is somehow invalid. You can also try deleting .CoronaLiveBuild file and trying again.
Deleting the livebuild file (which had been created on Windows building Android app) did the trick.
interesting difference between the livebuild files.
Windows has lowercase alpha. Mac has uppercase.
Should a Mac overwrite the livebuild file (present as I’m using common dropbox forder for builds)?
Sending you thelivebuild files anyway.
Thanks you. I think trick was in the line endings.
I guess Mac .CoronaLiveBuild file would work everywhere.
Conor,
What is 997? I think you’re looking at the wrong number. (Unless of course you mean 2016.2 997?)
Version numbers come in this format 2016.XXXX
Take a peek at your simulator when you first start it (see image) and you should see the version you’re using.
Thanks,
Ed
Sorry, it’s 2997, typo. Latest.
All good, just wanted to be sure.
Is there more information in the console log from the build?
Rob
This is the information from the console
Dec 06 07:45:40.036 Building ios app for conor@…com with 2016.2997
Dec 06 07:45:42.374 Using custom build id from app bundle: 00000 (AppSettings.lua)
Dec 06 07:45:42.705 BUILD ERROR: /var/folders/1x/8glztypj1fn_7_qk2dnv0fcm0000kr/T/CLtmpYr2u4f/main.lua:1: unfinished string near '‘6153def9-64a2-4335-a4c6-e5c09a7dbee6’
Dec 06 07:45:42.724 iOS build failed (5) after 0 seconds
Dec 06 07:45:43.120 ERROR: Build Failed: Error code: 5
Dec 06 07:45:43.120
Please note, the build executes properly if livebuild is not selected.
System is macincloud osx El Capitan 10.11.6
In case it’s relevant here are my plugins
plugins = { ["plugin.OneSignal"] = { publisherId = "com.onesignal", }, ["plugin.google.play.services"] = { publisherId = "com.coronalabs", supportedPlatforms = { android=true, ["android-kindle"]=true }, }, },Could you please PM me contents of .CoronaLiveBuild file you have in your project root? It seems that “key” property is somehow invalid. You can also try deleting .CoronaLiveBuild file and trying again.
Deleting the livebuild file (which had been created on Windows building Android app) did the trick.
interesting difference between the livebuild files.
Windows has lowercase alpha. Mac has uppercase.
Should a Mac overwrite the livebuild file (present as I’m using common dropbox forder for builds)?
Sending you thelivebuild files anyway.
Thanks you. I think trick was in the line endings.
I guess Mac .CoronaLiveBuild file would work everywhere.