Ionic Archive does not generate an IPA File

Archive Issues
,
1

Hi :slight_smile:

I’m enjoying bitrise so far. Has worked quite smoothly. One thing i cant get right, is that no IPA is generated by the Ionic Archive step.
This is what i think is the relevant output

Downloading provisioning profile: 2/3
Moving it to: /Users/vagrant/Library/MobileDevice/Provisioning Profiles/fcccf183-9e8d-4757-b52f-6848fb0b56c3.mobileprovision
iOS Team Store Provisioning Profile: xxxx
exportType: app-store
team: xxxx
bundleID: xxxx
capabitlities:
- aps-environment: production
- keychain-access-groups: [xxx.*]
- com.apple.developer.associated-domains: *
certificates:
- iPhone Distribution: xxxx
  serial: xxxxx
  teamID: xxxxx
expire: 2018-10-27 17:07:11 +0000 UTC
[!] xcode managed profile
Downloading provisioning profile: 3/3
Moving it to: /Users/vagrant/Library/MobileDevice/Provisioning Profiles/xxx-6845-475f-959b-9bbae2f97a3e.mobileprovision

Building for iPhone X Simulator
Building project: /Users/vagrant/git/platforms/ios/Myapp.xcworkspace
	Configuration: Release
	Platform: emulator
Build settings from command line:
    CONFIGURATION_BUILD_DIR = /Users/vagrant/git/platforms/ios/build/emulator
    SDKROOT = iphonesimulator11.2
    SHARED_PRECOMPS_DIR = /Users/vagrant/git/platforms/ios/build/sharedpch
Build settings from configuration file '/Users/vagrant/git/platforms/ios/cordova/build-release.xcconfig':
    CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES = YES
    CODE_SIGN_ENTITLEMENTS = $(PROJECT_DIR)/$(PROJECT_NAME)/Entitlements-$(CONFIGURATION).plist
    CODE_SIGN_IDENTITY = xxxxx
    DEVELOPMENT_TEAM = xxxxx
    ENABLE_BITCODE = NO
    HEADER_SEARCH_PATHS = "$(TARGET_BUILD_DIR)/usr/local/lib/include" "$(OBJROOT)/UninstalledProducts/include" "$(OBJROOT)/UninstalledProducts/$(PLATFORM_NAME)/include" "$(BUILT_PRODUCTS_DIR)"
    OTHER_LDFLAGS = -ObjC
    PROVISIONING_PROFILE = https:
    SWIFT_OBJC_BRIDGING_HEADER = $(PROJECT_DIR)/$(PROJECT_NAME)/Bridging-Header.h

End log of iOS Build:

        Signing Identity:     "-"
        /usr/bin/codesign --force --sign - --timestamp=none /Users/vagrant/git/platforms/ios/build/emulator/Myapp.app
    ** BUILD SUCCEEDED **
    IOS output dir exists!
    Collecting ios outputs
    The dsym dir path is now available in the Environment Variable: BITRISE_DSYM_DIR_PATH (value: /Users/vagrant/deploy/Myapp.app.dSYM)
    The dsym.zip path is now available in the Environment Variable: BITRISE_DSYM_PATH (value: /Users/vagrant/deploy/Myapp.app.dSYM.zip)
    The app dir path is now available in the Environment Variable: BITRISE_APP_DIR_PATH (value: /Users/vagrant/deploy/Myapp.app)
    The app.zip path is now available in the Environment Variable: BITRISE_APP_PATH (value: /Users/vagrant/deploy/Myapp.app.zip)

I’m wondering if the Signing Identity: “-” is an error or not. Does anybody have any ideas?

The [!] xcode managed profile worries me as well

Thank you so much

Best regards

2

Ok, so i had the Build Command Target set to emulator in Ionic Archive which led to no error for the IOS Code Signing.

When i changed it to device i got a proper error message. It was the Xcode managed Provisioning Profile error.

Got it sorted.

Thanks anyways

1 Like
3

Thanks for sharing @explofish! :slight_smile: