Nativescript-cli: "Cannot read property 'ExceptionMessage' of null" - when using tns publish ios and there an outage of iTunes

[briandilley]

I have a CI system that builds and pushes an Android version and an iOS version of the app to their respective app stores. This has been working for a while now, but suddenly has stopped working. This is the second time that this command has stopped working for whatever reason, I'm hoping this time it can actually be fixed because last time I just had to deal with it and do manual uploads until a new version of the tools came out where it started working again.

It seems to do the build and archive just fine, the problem looks like it's with uploading to the itunesconnect servers.

Here's the output.

** ARCHIVE SUCCEEDED **

2017-08-22 13:01:02.526 xcodebuild[8211:22224] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/jm/fw86rxds0xn69sk40d18y69m0000gp/T/quickridensmobile_2017-08-22_13-01-02.526.xcdistributionlogs'.
Exported quickridensmobile.xcarchive to: /Users/distiller/quickride-ns-mobile/platforms/ios/build/device
** EXPORT SUCCEEDED **

Project successfully built.
The server returned unexpected response: TypeError: Cannot read property 'ExceptionMessage' of null
# publish ios

┌───────────────┬───────────────────────────────────────────────────────────┐
│ Usage         │ Synopsis                                                  │
│ Build and     │ $ tns publish ios [<Apple ID> [<Password> [<Mobile        │
│ upload        │ Provisioning Profile Identifier> [<Code Sign Identity>]]] │
│ package       │ ]]                                                        │
│ Upload        │ $ tns publish ios [<Apple ID> [<Password>]] --ipa <Ipa    │
│ package       │ File Path>                                                │
└───────────────┴───────────────────────────────────────────────────────────┘

Uploads project to iTunes Connect. The command either issues a production build and uploads it to iTunes Connect, or uses an already built package to upload.

### Options

    * --ipa - If set, will use provided .ipa file instead of building the project.
    * --team-id - Specified the team id for which Xcode will try to find distribution certificate and provisioning profile when exporting for AppStore submission.

### Attributes

    * <Apple ID> and <Password> are your credentials for logging into iTunes Connect.
    * <Mobile Provisioning Profile Identifier> the identifier of the mobile provision(e.g. d5d40f61-b303-4fc8-aea3-fbb229a8171c) which will be used for building. This can easily be acquired through the iPhone Configuration Utility.
    * <Code Sign Identity> the code sign identity which will be used for building. You can set it to something generic like 'iPhone Distribution' to let the build automatically detect a code sign identity.

[basketofsoftkittens]

+1

[dtopuzov]

@briandilley @basketofsoftkittens
Can you give us some more details:

• Xcode version
• CLI version
• Exact command you run
• Do you have something additional set in App_Resources/iOS/build.xcconfig?

[briandilley]

Xcode version: 8.2
cl versioni: @next
command: tns publish ios [email protected] password_here provisioning_profile_uuid "iPhone Distribution: Company Name, LLC (ID NUMBER HERE)"

build.xcconfig:

ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_LAUNCHIMAGE_NAME = LaunchImage;

DEVELOPMENT_TEAM = XXXXX;
CODE_SIGN_IDENTITY = iPhone Distribution;
PROVISIONING_PROFILE = XXXXX;
APP_PROFILE = XXXXX;

TARGETED_DEVICE_FAMILY = 1;

CODE_SIGN_ENTITLEMENTS = quickridensmobile/quickridensmobile.entitlements

The command works fine locally on my workstation, but doesn't on the CI env... even though it was working fine yesterday.

[briandilley]

I take back the part about it working locally... it's broken locally as well.

The server returned unexpected response: TypeError: Cannot read property 'ExceptionMessage' of null

A better error message than that would be nice at a minimum, optimally fixing it.

[briandilley]

This may just be a problem with iTunes connect... they have this on their status page:

iTunes Connect - Issue
Today, 10:25 AM - ongoing
Some users are affected
Users are experiencing a problem with this service.

[dtopuzov]

Leaving the issue open since we should try to fix the error message in case of problems with iTunes Connect.

[briandilley]

I can confirm that it was an iTunes outage - everything works again :)