Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-25416] iOS: App is not installing on the device with Ti SDK 6.3.0.v20171017063048

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2017-10-30T21:14:24.000+0000
Affected Version/sRelease 6.3.0
Fix Version/sRelease 6.3.0
ComponentsiOS
Labelsn/a
ReporterMotiur Rahman
AssigneeFeon Sua Xin Miao
Created2017-10-20T01:23:35.000+0000
Updated2017-11-07T23:54:08.000+0000

Description

I am unable to run App on the device with the latest RC release. Always I get the following error [ERROR] : Invalid "--pp-uuid" value "84f52c42-df58-40e6-b133-7fe24409decc" For help, run: titanium.js help build On emulator, I got this error for Alloy App [ERROR] : Detected legacy "DefaultIcon.png/DefaultIcon-.png" in project directory. [ERROR] : Please move "DefaultIcon.png/DefaultIcon-.png" to "/app" for Alloy 1.10.0 or later. [ERROR] : Alloy compiler failed But If I move the image file as described then it works as expected. Thanks

Attachments

FileDateSize
appc ti info -t ios.txt2017-10-20T01:12:42.000+000018973
error.txt2017-10-24T01:56:07.000+0000864
New_appc ti info -t ios.txt2017-10-24T01:55:59.000+000019972
runningLog.txt2017-10-21T09:27:13.000+0000896

Comments

  1. Feon Sua Xin Miao 2017-10-20

    DefaultIcon.png will be handled by ALOY-1318. --pp-uuid error, I can't reproduce it. According to [~amukherjee], he couldn't either. ti info output looks fine. If anyone manage to reproduce, please provide debug output, logs. Thanks! [~morahman], please also attach debug output for DEBUG=* appc run -p ios -T device --pp-uuid 84f52c42-df58-40e6-b133-7fe24409decc
  2. Feon Sua Xin Miao 2017-10-23

    From the debug log, [ERROR] Specified provisioning profile UUID "779ed0a1-6ab2-439b-b30f-e39f23e90c2c" does not include the "Aziz Ahmad (63BQJ23J78)" certificate, it seems to be triggered by TIMOB-25318, which added stricter validation around provisioning profiles. [~morahman], can you try recreate a provisioning profile, make sure the dev cert is assigned to the provisioning profile.
  3. Motiur Rahman 2017-10-24

    Everything I have newly created development certificate, development provisioning profile but still facing the same issue. Please see the error.txt and New_appc ti info -t ios.txt file. Thanks
  4. Motiur Rahman 2017-10-24

    Finally, I can run successfully. The problem was with an expired development certificate. I had two certificates one is valid another on is expired. I deleted my expired certificate from the keychain >>My certificate category but it was still in "Certificate" category. My Old Ti SDK did not create any problem with that expired certificate but RC one was not able to detect the valid certificate and provisioning profile. After deleting that expired certificate it works as expected. Thanks [~fmiao].
  5. Francisco 2017-10-24

    Same here, after cleaning all the certificates from the keychain except the ones in use, I can now build the App and submit to the App Store.
  6. Feon Sua Xin Miao 2017-10-25

    master: https://github.com/appcelerator/titanium_mobile/pull/9553 6_3_X: https://github.com/appcelerator/titanium_mobile/pull/9554 *To Reproduce* 1. install more than one development certificate that has the same identify 2. for each of the certs, create a provisioning profile that has the cert assigned 3. remove the private key of the certificate that expires the earliest 4. build to device using --pp-uuid, passing each of the provisioning profile id. Please test with Xcode 9 & 8, for thoroughness 7 also. :)
  7. Eric Wieber 2017-10-30

    FR Passed. Able to see all valid profiles when trying to build with multiple certs with the same identity.

JSON Source