<!-- Thanks for your interest in using the App Center SDK for React Native. Please create issues only for problems specific to using the SDK for React Native. If your issue is related to App Center build only (meaning no issue building locally) or CodePush, please create an issue on https://github.com/Microsoft/appcenter instead. -->

Description

When deploying a codepush release to android we're getting the following error:

start android release --mandatory
Running "react-native bundle" command:

node node_modules/.bin/react-native bundle --assets-dest build/CodePush --bundle-output build/CodePush/index.android.bundle --dev false --entry-file index.js --platform android --sourcemap-output buildmap/index.android.bundle.map
Welcome to React Native!
                Learn once, write anywhere

info Writing bundle output to:, build/CodePush/index.android.bundle
info Writing sourcemap output to:, buildmap/index.android.bundle.map
info Done writing bundle output
info Done writing sourcemap output
info Copying 42 asset files
info Done copying assets
Error: Failed to release a CodePush update.
error Command failed with exit code 3.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I found several similar issues in this forum which seem to have been addressed with 2.7.3, but the problem persists for us.

Repro Steps

1. Run appcenter codepush release-react -a APP_HERE -d $CODEPUSH_ENV -t '3.0.0 - 3.11.0' --disable-duplicate-release-error --description $MANDATORY_STRING --output-dir build --sourcemap-output buildmap/index.android.bundle.map

Details

1. Which version of the App Center SDK are you using? appcenter version 2.7.3
2. Which OS version did you experience the issue on?
   • MacOS 11.1
3. Run the following command and paste the output below: react-native info

System:
    OS: macOS 11.1
    CPU: (8) x64 Apple M1
    Memory: 79.98 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.6.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.4.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.8743.12.41.6953283
    Xcode: 12.3/12C33 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.9.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    *react-native*: Not Found

Hi! Thanks for getting in touch with us! It does not look like the SDK question. Could you please open a support ticket via the App Center Portal. You can find the help menu in the upper right corner of the App Center portal: ? > Contact support.

I have also a problem with installing ios app from App Center. The downloading seem ok. I can see the .ipa file in Files. The blue dot appears beside the app logo but there is no installation of the new file. On the installation page I get this message "App Center requires JavaScript" I have enabled the JavaScript in the browser, but nothing happens.

Hi - I'm trying to use App Center to build and distribute an app via App Store Connect. We are trying to integrate a NuGet package (Ensighten.FormsPlugin) that has a bound Swift library and is targeting iOS < 12.2 so it requires SwiftSupport bundled within the IPA. There are several NuGet packages that are designed to provide this but none appear to be compatible with App Center distribution process. Submitting through XCode directly works correctly but our app is deeply integrated with App Center / CI and submitting the package locally through XCode is not an option.

We've created a few sample projects that demonstrate the issue.

Submitted without Errors but crashes on iOS < 12.2 (Ensighten Only): https://bitbucket.org/ensighten-ondemand/xamarintestinng/src/ensighten-only/

** Submission Rejected due to SwiftSupport missing (using Xamarin.iOS.SwiftRuntime):** https://bitbucket.org/ensighten-ondemand/xamarintestinng/src/ensighten-swift/ Received "ITMS-90426: Invalid Swift Support" error from Apple

** Submission Rejected due to Invalid Signature / Improperly Signed (using Xamarin.iOS.SwiftRuntime and Xamarin.Swift4):** https://bitbucket.org/ensighten-ondemand/xamarintestinng/src/ensighten-xamarin-swift-runtime/ invalid-signature-log.txt

Is it possible to add support so that Apps targeting iOS < 12.2 that have embedded Swift Support can be distributed through App Center?

@botatoes Has this been added to the roadmap? We don't want to migrate away from app center's wonderful features simply because it can't handle the OBB files when using it with unity projects!

Hello!

Description

Now it's not possible to use AppCenterReactNativeShared on M1 macbooks - because AppCenterReactNativeShared.framework doesn't contain arm64/iphonesimulatorsdk library

Repro Steps

1. Create RN-project
2. Add appcenter package
3. Try to build it on M1-device

Details

1. App Center SDK v4.1.0

2. iOS 14

3. iPhone Simulator

5. Build xcode project

6. All versions of cocoapods

7. /Pods/AppCenterReactNativeShared/AppCenterReactNativeShared/AppCenterReactNativeShared.framework/AppCenterReactNativeShared' for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

<!-- Thanks for your interest in using the App Center SDK for React Native. Please create issues only for problems specific to using the SDK for React Native. If your issue is related to App Center build only (meaning no issue building locally) or CodePush, please create an issue on https://github.com/Microsoft/appcenter instead. -->

Description

When deploying a codepush release to android we're getting the following error:

start android release --mandatory
Running "react-native bundle" command:

node node_modules/.bin/react-native bundle --assets-dest build/CodePush --bundle-output build/CodePush/index.android.bundle --dev false --entry-file index.js --platform android --sourcemap-output buildmap/index.android.bundle.map
Welcome to React Native!
                Learn once, write anywhere

info Writing bundle output to:, build/CodePush/index.android.bundle
info Writing sourcemap output to:, buildmap/index.android.bundle.map
info Done writing bundle output
info Done writing sourcemap output
info Copying 42 asset files
info Done copying assets
Error: Failed to release a CodePush update.
error Command failed with exit code 3.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I found several similar issues in the issue which seem to have been address with 2.7.3, but the problem persists for us.

Please describe the issue you are facing using the SDK.

Repro Steps

1. Run appcenter codepush release-react -a APP_HERE -d $CODEPUSH_ENV -t '3.0.0 - 3.11.0' --disable-duplicate-release-error --description $MANDATORY_STRING --output-dir build --sourcemap-output buildmap/index.android.bundle.map

Details

1. Which version of the App Center SDK are you using? appcenter version 2.7.3
2. Which OS version did you experience the issue on?
   • MacOS 11.1
3. Run the following command and paste the output below: react-native info

System:
    OS: macOS 11.1
    CPU: (8) x64 Apple M1
    Memory: 79.98 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.6.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.4.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.8743.12.41.6953283
    Xcode: 12.3/12C33 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.9.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    *react-native*: Not Found

Currently only the "regular" release contains plcrashutil, so the people who want to use one of the other 2 choices, need to download both zips. It would be nice to have the tools included in all 3 zips

Hello @russelarms, I think there is still a lot of documentation that could be added. How AppCenter resolves dependancies with Carthage, pods, etc. is not documented and this hidden logic makes it hard to use AppCenter when things go wrong

Hey @russelarms , no not yet. The issue is still open. I have uninstalled/reinstalled everything several times to make sure I did not miss a step but still seeing this error. I actually migrated another app to iOS and codepush is working fine there. I compared the configuration with the app in question and everything is the same.

Mind taking a quick look at my code?

Info.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleDevelopmentRegion</key>
	<string>en</string>
	<key>CFBundleDisplayName</key>
	<string>PASSWORDRESET</string>
	<key>CFBundleExecutable</key>
	<string>$(EXECUTABLE_NAME)</string>
	<key>CFBundleIdentifier</key>
	<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>$(PRODUCT_NAME)</string>
	<key>CFBundlePackageType</key>
	<string>APPL</string>
	<key>CFBundleShortVersionString</key>
	<string>$(MARKETING_VERSION)</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>$(CURRENT_PROJECT_VERSION)</string>
	<key>CodePushDeploymentKey</key>
	<string>PwifFf1Vwr7sEF95F4m8vqMSzimSxR88x4NWL</string>
	<key>LSRequiresIPhoneOS</key>
	<true/>
	<key>NSAppTransportSecurity</key>
	<dict>
		<key>NSAllowsArbitraryLoads</key>
		<true/>
		<key>NSExceptionDomains</key>
		<dict>
			<key>localhost</key>
			<dict>
				<key>NSExceptionAllowsInsecureHTTPLoads</key>
				<true/>
			</dict>
		</dict>
	</dict>
	<key>NSLocationWhenInUseUsageDescription</key>
	<string></string>
	<key>UIAppFonts</key>
	<array>
		<string>OpenSans-Bold.ttf</string>
		<string>OpenSans-Regular.ttf</string>
		<string>ProximaNova-Bold.ttf</string>
		<string>ProximaNova-Light.ttf</string>
		<string>ProximaNova-Regular.ttf</string>
	</array>
	<key>UILaunchStoryboardName</key>
	<string>LaunchScreen</string>
	<key>UIRequiredDeviceCapabilities</key>
	<array>
		<string>armv7</string>
	</array>
	<key>UISupportedInterfaceOrientations</key>
	<array>
		<string>UIInterfaceOrientationPortrait</string>
		<string>UIInterfaceOrientationLandscapeLeft</string>
		<string>UIInterfaceOrientationLandscapeRight</string>
	</array>
	<key>UIViewControllerBasedStatusBarAppearance</key>
	<false/>
</dict>
</plist>

AppDelegate.m

#import "AppDelegate.h"

#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
#import <CodePush/CodePush.h>

#ifdef FB_SONARKIT_ENABLED
#import <FlipperKit/FlipperClient.h>
#import <FlipperKitLayoutPlugin/FlipperKitLayoutPlugin.h>
#import <FlipperKitUserDefaultsPlugin/FKUserDefaultsPlugin.h>
#import <FlipperKitNetworkPlugin/FlipperKitNetworkPlugin.h>
#import <SKIOSNetworkPlugin/SKIOSNetworkAdapter.h>
#import <FlipperKitReactPlugin/FlipperKitReactPlugin.h>

static void InitializeFlipper(UIApplication *application) {
  FlipperClient *client = [FlipperClient sharedClient];
  SKDescriptorMapper *layoutDescriptorMapper = [[SKDescriptorMapper alloc] initWithDefaults];
  [client addPlugin:[[FlipperKitLayoutPlugin alloc] initWithRootNode:application withDescriptorMapper:layoutDescriptorMapper]];
  [client addPlugin:[[FKUserDefaultsPlugin alloc] initWithSuiteName:nil]];
  [client addPlugin:[FlipperKitReactPlugin new]];
  [client addPlugin:[[FlipperKitNetworkPlugin alloc] initWithNetworkAdapter:[SKIOSNetworkAdapter new]]];
  [client start];
}
#endif

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
#ifdef FB_SONARKIT_ENABLED
  InitializeFlipper(application);
#endif

  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"PASSWORDRESET"
                                            initialProperties:nil];

  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];
  return YES;
}

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
  #if DEBUG
    return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  #else
    return [CodePush bundleURL];
  #endif
}

@end

Package.json

"dependencies": {
  "@react-native-community/netinfo": "^5.9.7",
  "@tradle/react-native-http": "^2.0.0",
  "assert": "^1.1.1",
  "axios": "^0.19.0",
  "browserify-zlib": "^0.1.4",
  "console-browserify": "^1.1.0",
  "constants-browserify": "^1.0.0",
  "dns.js": "^1.0.1",
  "domain-browser": "^1.1.1",
  "events": "^1.0.0",
  "https-browserify": "0.0.1",
  "path-browserify": "0.0.0",
  "process": "^0.11.0",
  "punycode": "^1.2.4",
  "querystring-es3": "^0.2.1",
  "react": "16.13.1",
  "react-native": "^0.63.3",
  "react-native-code-push": "^6.3.0",
  "react-native-crypto": "^2.2.0",
  "react-native-gesture-handler": "^1.8.0",
  "react-native-level-fs": "^3.0.0",
  "react-native-os": "^1.2.6",
  "react-native-randombytes": "^3.6.0",
  "react-native-screens": "^2.15.0",
  "react-native-simple-radio-button": "^2.7.4",
  "react-native-snackbar-component": "^1.1.10",
  "react-native-tcp": "^3.3.2",
  "react-native-udp": "^2.7.0",
  "react-navigation": "^4.0.10",
  "react-navigation-stack": "^1.9.4",
  "readable-stream": "^1.0.33",
  "stream-browserify": "^1.0.0",
  "string_decoder": "^0.10.31",
  "timers-browserify": "^1.0.1",
  "toggle-switch-react-native": "^2.3.0",
  "tty-browserify": "0.0.0",
  "url": "^0.10.3",
  "util": "^0.10.4",
  "vm-browserify": "0.0.4"
},

We're seeing lots of crashes that we cannot reproduce and look exactly like in microsoft/appcenter-sdk-apple#1944 . Any chances support for the ASI is going to be implemented?

After updating to 2.5.1, cannot login anymore

TeamCity$ appcenter login --token <mytoken>
internal/modules/cjs/loader.js:614
  throw e;
  ^

Error: No valid exports main found for '/usr/local/lib/node_modules/appcenter-cli/node_modules/uuid'
    at resolveExportsTarget (internal/modules/cjs/loader.js:611:9)
    at applyExports (internal/modules/cjs/loader.js:492:14)
    at resolveExports (internal/modules/cjs/loader.js:541:12)
    at Function.Module._findPath (internal/modules/cjs/loader.js:643:22)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:941:27)
    at Function.Module._load (internal/modules/cjs/loader.js:847:27)
    at Module.require (internal/modules/cjs/loader.js:1016:19)
    at require (internal/modules/cjs/helpers.js:69:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/appcenter-cli/dist/util/apis/telemetry-filter.js:7:16)
    at Module._compile (internal/modules/cjs/loader.js:1121:30) {
  code: 'MODULE_NOT_FOUND'
}

CLI is broken for our project, it looks like, to use the upload. Not sure why but testing out in postman gives me a 404 error that it can't find the project even though I can upload it using the current API that you are killing.

JFYI we have an updated instruction on the new API: https://docs.microsoft.com/en-us/appcenter/distribution/uploading#upload-new-release

Hi, @grndvl1, sorry you are experiencing issues.

Regarding the telemetry question format: it's working fine for me, could you share some information about the environment (os, terminal, node, npm versions) where you're experiencing this issue?

Why do I need userid in-app when I am using the appcenter token?

This is likely because users can share access to their applications with other users. In this case, appcenter apps list will show something like

yourUserId/AppName
otherUserId/AppName

Our app name has - dashes in it and this might be messing up.

Could you please describe the dash problem in more detail?

We have a legacy group from Hockey called "Tag: our-qa", well guess what setting this in --group, it fails.

Have you tried escaping space char (\ on macOS)?

Not sure why but testing out in postman gives me a 404 error that it can't find the project even though I can upload it using the current API that you are killing.

Can you please file a support ticket with us so we can look into your specific issues and logs? https://docs.microsoft.com/en-us/appcenter/general/support-center#contact-us

Hi @grndvl1! There's built-in help command, could you point us to what is missing?

appcenter distribute release --help

Upload release binary and trigger distribution, at least one of --store or --group must be specified

Usage: appcenter distribute release -f|--file <arg> [--mandatory] [--silent] [-R|--release-notes-file <arg>]
         [-r|--release-notes <arg>] [-s|--store <arg>] [-g|--group <arg>] [-n|--build-number <arg>]
         [-b|--build-version <arg>] [-a|--app <arg>]

Options:
    -f|--file <arg>                           Path to binary file                                                     
       --mandatory                            Make the release mandatory for the testers (default is false)           
       --silent                               Do not notify testers of this release                                   
    -R|--release-notes-file <arg>             Path to release notes file                                              
    -r|--release-notes <arg>                  Release notes text                                                      
    -s|--store <arg>                          Store name                                                              
    -g|--group <arg>                          Distribution group name                                                 
    -n|--build-number <arg>                   Build number parameter required for macOS .pkg and .dmg files           
    -b|--build-version <arg>                  Build version parameter required for .zip, .msi, .pkg and .dmg files    
    -a|--app <arg>                            Specify app in the <ownerName>/<appName> format                         

Common Options (works on all commands):
       --disable-telemetry             Disable telemetry for this command                                             
    -v|--version                       Display appcenter version                                                      
       --quiet                         Auto-confirm any prompts without waiting for input                             
    -h|--help                          Display help for current command                                               
       --env <arg>                     Environment when using API token                                               
       --token <arg>                   API token                                                                      
       --output <arg>                  Output format: json                                                            
       --debug                         Display extra output for debugging

Hi @MOwais, did you manage to solve this problem?

Hi @alexDtorres, sorry for the delay! I confirm it's a bug. After changing the name we need to execute: appcenter apps set-current *updated_name* The PR is welcome :)

Hi, @Zeropointer11, as far as I know, release notes are handled as plain text throughout App Center.