iOS and Android standalone builds are suddenly failing

Worked fine until Friday(09/13). Not sure what the problem is.

We need to create the production builds this week. Would appreciate a prompt response. -Thanks

ios: https://expo.io/builds/50abe013-82e7-431b-85d3-d6440d3a6db4
android: https://expo.io/builds/9a395ab8-66c5-4713-8269-74786fb45232

App.json

{
  "expo": {
    "sdkVersion": "34.0.0",
    "orientation": "portrait",
    "name": "xxx",
    "icon": "./assets/images/AppIcon.png",
    "version": "1.0.0",
    "slug": "xxx",
    "hooks": {
      "postPublish": [
        {
          "file": "sentry-expo/upload-sourcemaps",
          "config": {
            "organization": "xxx",
            "project": "mobile",
            "authToken": "*******"
          }
        }
      ]
    },
    "scheme": "tnet",
    "splash": {
      "image": "./assets/images/launch-screen.png"
    },
    "updates": {
      "fallbackToCacheTimeout": 1000
    },
    "assetBundlePatterns": [
      "assets/*"
    ],
    "notification": {
      "icon": "assets/images/notification-icon.png",
      "color": "#F47B27"
    },
    "ios": {
      "bundleIdentifier": "xxx",
      "infoPlist": {
        "NSFaceIDUsageDescription": "This app will optionally use Face ID or Touch ID to save login"
      },
      "supportsTablet": true
    },
    "android": {
      "adaptiveIcon": {
        "foregroundImage": "./assets/images/adaptive-icon-fg.png"
      },
      "package": "xxx",
      "googleServicesFile": "./assets/config/builds/non-prod/google-services.json",
      "versionCode": 828,
      "permissions": [
        "ACCESS_COARSE_LOCATION",
        "ACCESS_FINE_LOCATION",
        "CAMERA",
        "CAMERA_ROLL",
        "MANAGE_DOCUMENTS",
        "READ_CONTACTS",
        "READ_CALENDAR",
        "WRITE_CALENDAR",
        "READ_EXTERNAL_STORAGE",
        "READ_PHONE_STATE",
        "RECORD_AUDIO",
        "USE_FINGERPRINT",
        "VIBRATE",
        "WAKE_LOCK",
        "WRITE_EXTERNAL_STORAGE",
        "com.anddoes.launcher.permission.UPDATE_COUNT",
        "com.android.launcher.permission.INSTALL_SHORTCUT",
        "com.google.android.c2dm.permission.RECEIVE",
        "com.google.android.gms.permission.ACTIVITY_RECOGNITION",
        "com.google.android.providers.gsf.permission.READ_GSERVICES",
        "com.htc.launcher.permission.READ_SETTINGS",
        "com.htc.launcher.permission.UPDATE_SHORTCUT",
        "com.majeur.launcher.permission.UPDATE_BADGE",
        "com.sec.android.provider.badge.permission.READ",
        "com.sec.android.provider.badge.permission.WRITE",
        "com.sonyericsson.home.permission.BROADCAST_BADGE"
      ]
    }
  }
}

Expo Diagnostics:

Expo CLI 3.0.9 environment info:
System:
OS: macOS 10.14.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.13.0 - ~/.nvm/versions/node/v10.13.0/bin/node
Yarn: 1.10.0 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.13.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.1 AI-173.4720617
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
@storybook/react-native: 4.1.18 => 4.1.18
expo: 34.0.3 => 34.0.3
react: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-34.0.0.tar.gz => 0.59.8
react-navigation: 2.18.3 => 2.18.3

The iOS error is as follow:

ERROR [2019-09-16 22:38:44.66]: Looks like fastlane ran into a build/archive error with your project
ERROR [2019-09-16 22:38:44.66]: It's hard to tell what's causing the error, so we wrote some guides on how
ERROR [2019-09-16 22:38:44.66]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
ERROR [2019-09-16 22:38:44.66]: Before submitting an issue on GitHub, please follow the guide above and make
ERROR [2019-09-16 22:38:44.66]: sure your project is set up correctly.
ERROR [2019-09-16 22:38:44.66]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
ERROR [2019-09-16 22:38:44.66]: the full commands printed out in yellow in the above log.
ERROR [2019-09-16 22:38:44.66]: Make sure to inspect the output above, as usually you'll find more error information there
INFO [2019-09-16 22:38:44.66]: 
[stderr] /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/fastlane_core/lib/fastlane_core/ui/interface.rb:163:in `build_failure!': [!] Error packaging up the application (FastlaneCore::Interface::FastlaneBuildFailure)
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/error_handler.rb:112:in `handle_package_error'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/runner.rb:138:in `block in package_app'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/fastlane_core/lib/fastlane_core/command_executor.rb:89:in `execute'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/runner.rb:134:in `package_app'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/runner.rb:27:in `run'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/manager.rb:19:in `work'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/commands_generator.rb:44:in `block (2 levels) in run'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/commands_generator.rb:75:in `run'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/gym/lib/gym/commands_generator.rb:15:in `start'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
[stderr] 	from /usr/local/lib/ruby/gems/2.4.0/gems/fastlane-2.116.1/bin/fastlane:23:in `<top (required)>'
[stderr] 	from /usr/local/bin/fastlane:23:in `load'
[stderr] 	from /usr/local/bin/fastlane:23:in `<main>'
removed provisioning profile from the home directory
Error: fastlane exited with non-zero code: 1
    at ChildProcess.completionListener (/usr/local/turtle-js/node_modules/@expo/xdl/node_modules/@expo/spawn-async/build/spawnAsync.js:52:23)

@sjchmiela @quinlanj @adamjnav @ide

on ios there is error in logs

"Provisioning profile "TriNet Mobile v7 (Distribution)" expired on Sep 14, 2019.

on android there is some network issue, have you tried running android build more than once?

@wkozyra Thank you! Its working now.

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.