Problem submitting iOS app created using react native - react-native

I created a react native app, ran eas build --platform iOS
then ran
eas submit -p iOS
I also tried using Transporter.
here's the output and error:
andrewtriboletti#andrews-mbp JawnSocial % eas submit -p ios
Ensuring your app exists on App Store Connect. This step can be skipped by providing ascAppId in the submit profile.
Learn more: https://expo.fyi/asc-app-id
› Log in to your Apple Developer account to continue
✔ Apple ID: … andy.triboletti#gmail.com
› Restoring session /Users/andrewtriboletti/.app-store/auth/andy.triboletti#gmail.com/cookie
› Team GreenRobot LLC (779S839979)
› Provider GreenRobot LLC (12273)
✔ Logged in Local session
✔ Bundle identifier registered com.greenrobot.JawnSocial
✔ Prepared App Store Connect for JawnSocial com.greenrobot.JawnSocial
✔ What would you like to submit? › Select a build from EAS
✔ Which build would you like to submit? › - ID: b09b94ac-adf9-43ef-b2be-3aab0d3f1ec0 (1 hour ago)
Looking up credentials configuration for com.greenrobot.JawnSocial...
✔ Select what to use for your project: › [Add a new ASC API Key]
✔ Generate a new App Store Connect API Key? … yes
✔ Created App Store Connect API Key.
✔ Created App Store Connect API Key
✔ App Store Connect API Key assigned to JawnSocial: com.greenrobot.JawnSocial for EAS Submit.
Using API Key ID: 6W4JT5AB87 ([Expo] EAS Submit TpemZYAU_k)
ASC App ID: 1659700891
Project ID: b2792c43-f381-4595-bec4-029e735b6758
App Store Connect API Key:
Key Name : [Expo] EAS Submit TpemZYAU_k
Key ID : 6W4JT5AB87
Key Source: EAS servers
Build:
Build ID : b09b94ac-adf9-43ef-b2be-3aab0d3f1ec0
Build Date : 12/13/2022, 1:42:44 PM
App Version : 1.0.0
Build number: 1
✔ Scheduled iOS submission
Submission details: https://expo.dev/accounts/andyt443/projects/JawnSocial/submissions/f4dc0e5c-8e69-48f7-8b9e-c35a83a478d3
Waiting for submission to complete. You can press Ctrl+C to exit.
✖ Something went wrong when submitting your app to Apple App Store Connect.
We couldn't figure out what went wrong. See logs to learn more.
[logs] Starting the submit process
[logs] Downloading archive
[logs] Preparing artifact
[logs] Verifying archive
[logs] Creating ascApiJsonKey.json file with ASC credentials
[logs] Submitting iOS app to TestFlight...
[logs] Submitting the app with fastlane pilot
[logs] -------------------
[logs] --- Step: pilot ---
[logs] -------------------
[logs] Creating authorization token for App Store Connect API
[logs] Ready to upload new build to TestFlight (App: 1659700891)...
[logs] Going to upload updated app to App Store Connect
[logs] This might take a few minutes. Please don't interrupt the script.
[logs] [altool] 2022-12-13 13:11:05.326 *** Error: The provided entity includes a relationship with an invalid value '1659700891' is not a valid ID for this relationship. (ID: 69084673-477e-4fd0-ab0d-06f50581a67f) (409)
[logs] [altool] {
[logs]
[logs] [altool] NSLocalizedDescription = "The provided entity includes a relationship with an invalid value";
[logs]
[logs] [altool] NSLocalizedFailureReason = "'1659700891' is not a valid ID for this relationship. (ID: 69084673-477e-4fd0-ab0d-06f50581a67f)";
[logs]
[logs] [altool] "original_server_error" = {
[logs]
[logs] [altool] code = "ENTITY_ERROR.RELATIONSHIP.INVALID";
[logs] [altool] detail = "'1659700891' is not a valid ID for this relationship.";
[logs]
[logs] [altool] id = "69084673-477e-4fd0-ab0d-06f50581a67f";
[logs]
[logs] [altool] source = {
[logs]
[logs] [altool] pointer = "/data/relationships/app/data/id";
[logs]
[logs] [altool] };
[logs] [altool] status = 409;
[logs]
[logs] [altool] title = "The provided entity includes a relationship with an invalid value";
[logs]
[logs] [altool] };
[logs]
[logs] [altool] }
[logs] Application Loader output above ^
[logs] Error uploading '/var/folders/h2/gp9wlkv11lg0qj6y2mnqgc_40000gn/T/ffc5114d-d1a8-43c6-81d9-ab4131a12c98.ipa'.
[logs] The provided entity includes a relationship with an invalid value '1659700891' is not a valid ID for this relationship. (ID: 69084673-477e-4fd0-ab0d-06f50581a67f) (409)
[logs] The call to the altool completed with a non-zero exit status: 1. This indicates a failure.
[logs] Could not download/upload from App Store Connect!
[logs] [!] Error uploading ipa file:
[logs] [Application Loader Error Output]: Error uploading '/var/folders/h2/gp9wlkv11lg0qj6y2mnqgc_40000gn/T/ffc5114d-d1a8-43c6-81d9-ab4131a12c98.ipa'.
[logs] [Application Loader Error Output]: The provided entity includes a relationship with an invalid value '1659700891' is not a valid ID for this relationship. (ID: 69084673-477e-4fd0-ab0d-06f50581a67f) (409)
[logs] [Application Loader Error Output]: The call to the altool completed with a non-zero exit status: 1. This indicates a failure.
[logs] Fastlane pilot failed
[logs] Failed to submit the app

I added
"buildNumber": "1",
To app.json. Then it worked.

Related

Appcenter build successful but can't find APK file - React Native

We are facing issues with React-Native in AppCenter. We are Once I run the build, everything goes well but at end we are facing below issue.
No addition pre or post script added in AppCenter.
Execution optimizations have been disabled for 12 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
**BUILD SUCCESSFUL** in 11m 32s
362 actionable tasks: 351 executed, 11 up-to-date
##[section]Finishing: Gradle Task
##[section]Starting: Android Postprocess
==============================================================================
Task : Shell script
Description : Run a shell script using Bash
Version : 2.212.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/shell-script
==============================================================================
[command]/bin/bash /Users/runner/runners/2.214.1/scripts/android-postprocess.sh /Users/runner/work/1/s/android/app/build/outputs/apk
Removing all ABI or density dependent APKs…
Found 0 APK file(s)
Found 0 unaligned APK file(s)
~/work/1/s/android/app/build/outputs ~/runners/2.214.1/scripts
~/runners/2.214.1/scripts
##[section]Async Command Start: Add Build Tag
Build '16' has following tags now: normal, android-app-bundle, javascript, android, manual, signed, mapping, distribution
##[section]Async Command End: Add Build Tag
##[section]Finishing: Android Postprocess
##[section]Starting: Sign APK
==============================================================================
Task : Android signing
Description : Sign and align Android APK files
Version : 3.201.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/android-signing
==============================================================================
##****[error]Error: No matching files were found with search pattern: ****/Users/runner/work/1/s/android/app/build/**/*.apk
##[section]Finishing: Sign APK
##[section]Starting: Sign APK
==============================================================================
Task : Android signing
Description : Sign and align Android APK files
Version : 3.201.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/android-signing
==============================================================================
##[section]Finishing: Sign APK
##[section]Starting: Checkout XXXXXXX#development to s
==============================================================================
Task : Get sources
Description : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
Version : 1.0.0
Author : Microsoft
Help : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
==============================================================================
Cleaning any cached credential from repository: XXXXXXX (ExternalGit)
##[section]Finishing: Checkout XXXXXXX#development to s
##[section]Starting: Finalize Job
Cleaning up task key
Start cleaning up orphan processes.
Terminate orphan process: pid (23181) (java)
Terminate orphan process: pid (22867) (java)
Terminate orphan process: pid (11113) (java)
Terminate orphan process: pid (7987) (java)
##[section]Finishing: Finalize Job
##[section]Finishing: Build
I tried with all the options but unable to resolve the issues.
I got the answer of my own question. As per Appcenter document you need to set universalApk to true. This is the only way in Appcenter weather you plan to make multiple apk to reduce the size.

Github author info

I'm using Github as a source in code build and using webhook (PULL_REQUEST_CREATED, PULL_REQUEST_UPDATED, PULL_REQUEST_REOPENED), but when I generate a pull request or update a pull request I want to access the last commit author info ( author name and email )
I'm using command : git log -1 --format="%an <%ae>"
But it will throw an error
[Container] 2022/07/08 18:17:46 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: git log -1 --format="%an <%ae>". Reason: exit status 128
I'm not able to access author info based on the last commit, I thought code build would clone the repo fully and able to access the last commit author info but it seems not

Problem Restoring NuGet Packages in GitHub ASP.NET Core repository

After performing the following steps:
git clone https://github.com/dotnet/aspnetcore.git
git checkout v3.0.0-preview8.19405.7
and navigating to src\Mvc:
dotnet restore
I get the following error:
C:\Program Files\dotnet\sdk\3.0.100-preview8-013656\NuGet.targets(123,5): error : Unable to load the service index for source https://dotnet.myget.org/F/roslyn/api/v3/index.json. [D:\aspnetcore\src\Mvc\Mvc.sln]
C:\Program Files\dotnet\sdk\3.0.100-preview8-013656\NuGet.targets(123,5): error : The SSL connection could not be established, see inner exception. [D:\aspnetcore\src\Mvc\Mvc.sln]
C:\Program Files\dotnet\sdk\3.0.100-preview8-013656\NuGet.targets(123,5): error : The remote certificate is invalid according to the validation procedure. [D:\aspnetcore\src\Mvc\Mvc.sln]

Attempting to install to be continuous with OpenShift 4 and self-managed GitLab

Following the instructions from here, I'm attempting to get to-be-continuous up and running.
I've created the empty to-be-continuous root group and the Maintainer non-individual GitLab account, and generated its appropriately scoped personal access token.
Upon executing the curl command to recursively copy the tbc group, I notice that the tools sub-group isn't cloned.
Seeing that the tracking repo from the tools group is required for the next step, I manually created the tools sub-group and individually manually cloned each of the repos under it, effectively mirroring the structure and content of the authoritative tbc repo.
Additionally I've configured my self-hosted GitLab's CA in the OpenShift GitLab runner so that I no longer get x509 errors.
With the above in place, including an available GitLab runner on my OpenShift cluster, I attempted to manually run the tracking repo's pipeline (as I understand this to be prerequisite to any other pipeline runs?).
The GitLab runner seemed to pick up the pipeline, as runner's log scrolled off the following:
Checking for jobs... received [0;m job[0;m=6103 repo_url[0;m=https://git.corp.odfl.com/to-be-continuous/tools/tracking.git runner[0;m=b3CyGtqD
Checking for jobs... received [0;m job[0;m=6104 repo_url[0;m=https://git.corp.odfl.com/to-be-continuous/tools/tracking.git runner[0;m=b3CyGtqD
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
Checking for jobs... received [0;m job[0;m=6105 repo_url[0;m=https://git.corp.odfl.com/to-be-continuous/tools/tracking.git runner[0;m=b3CyGtqD
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[0;33mWARNING: Job failed: command terminated with exit code 1[0;m [0;33mduration_s[0;m=9.30956493 [0;33mjob[0;m=6103 [0;33mproject[0;m=876 [0;33mrunner[0;m=b3CyGtqD
[0;33mWARNING: Failed to process runner [0;m [0;33mbuilds[0;m=2 [0;33merror[0;m=command terminated with exit code 1 [0;33mexecutor[0;m=kubernetes [0;33mrunner[0;m=b3CyGtqD
[0;33mWARNING: Job failed: command terminated with exit code 1[0;m [0;33mduration_s[0;m=9.808499871 [0;33mjob[0;m=6105 [0;33mproject[0;m=876 [0;33mrunner[0;m=b3CyGtqD
[0;33mWARNING: Failed to process runner [0;m [0;33mbuilds[0;m=1 [0;33merror[0;m=command terminated with exit code 1 [0;33mexecutor[0;m=kubernetes [0;33mrunner[0;m=b3CyGtqD
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
[31;1mERROR: Could not create cache adapter [0;m [31;1merror[0;m=cache factory not found: factory for cache adapter "" was not registered
Job succeeded [0;m duration_s[0;m=30.342517342 job[0;m=6104 project[0;m=876 runner[0;m=b3CyGtqD
At the same time, the pipeline log on GitLab shows the following:
Running with gitlab-runner 14.1.0 (8925d9a0)
on gitlab-runner-runner-5bc5455cfb-pmrpl b3CyGtqD
Preparing the "kubernetes" executor
00:00
Using Kubernetes namespace: dle-test
Using Kubernetes executor with image hadolint/hadolint:latest-alpine ...
Using attach strategy to execute scripts...
Preparing environment
00:07
Waiting for pod dle-test/runner-b3cygtqd-project-876-concurrent-0fvm2z to be running, status is Pending
Waiting for pod dle-test/runner-b3cygtqd-project-876-concurrent-0fvm2z to be running, status is Pending
ContainersNotInitialized: "containers with incomplete status: [init-logs]"
ContainersNotReady: "containers with unready status: [build helper]"
ContainersNotReady: "containers with unready status: [build helper]"
Running on runner-b3cygtqd-project-876-concurrent-0fvm2z via gitlab-runner-runner-5bc5455cfb-pmrpl...
Getting source from Git repository
00:01
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/b3CyGtqD/0/to-be-continuous/tools/tracking/.git/
Created fresh repository.
Checking out e31d6d28 as master...
Skipping Git submodules setup
Executing "step_script" stage of the job script
00:01
$ # BEGSCRIPT # collapsed multi-line command
/scripts-876-6103/step_script: eval: line 162: can't create /etc/ssl/certs/ca-certificates.crt: Permission denied
Uploading artifacts for failed job
00:00
Uploading artifacts...
WARNING: reports/hadolint-*.json: no matching files
ERROR: No files to upload
Uploading artifacts...
WARNING: reports/hadolint-*.json: no matching files
ERROR: No files to upload
Cleaning up file based variables
00:01
ERROR: Job failed: command terminated with exit code 1
Having spent quite a few hours getting this far, I'm stumped. Any idea what I'm doing wrong?
Added kaniko log as requested:
Running with gitlab-runner 14.1.0 (8925d9a0)
on gitlab-runner-runner-5bc5455cfb-4ggsp n8KiyZgX
Preparing the "kubernetes" executor
00:00
Using Kubernetes namespace: dle-test
Using Kubernetes executor with image gcr.io/kaniko-project/executor:debug ...
Using attach strategy to execute scripts...
Preparing environment
00:13
Waiting for pod dle-test/runner-n8kiyzgx-project-876-concurrent-0knvl9 to be running, status is Pending
Waiting for pod dle-test/runner-n8kiyzgx-project-876-concurrent-0knvl9 to be running, status is Pending
ContainersNotInitialized: "containers with incomplete status: [init-logs]"
ContainersNotReady: "containers with unready status: [build helper]"
ContainersNotReady: "containers with unready status: [build helper]"
Waiting for pod dle-test/runner-n8kiyzgx-project-876-concurrent-0knvl9 to be running, status is Pending
ContainersNotReady: "containers with unready status: [build helper]"
ContainersNotReady: "containers with unready status: [build helper]"
Waiting for pod dle-test/runner-n8kiyzgx-project-876-concurrent-0knvl9 to be running, status is Pending
ContainersNotReady: "containers with unready status: [build helper]"
ContainersNotReady: "containers with unready status: [build helper]"
Running on runner-n8kiyzgx-project-876-concurrent-0knvl9 via gitlab-runner-runner-5bc5455cfb-4ggsp...
Getting source from Git repository
00:02
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/n8KiyZgX/0/to-be-continuous/tools/tracking/.git/
Created fresh repository.
Checking out e31d6d28 as master...
Skipping Git submodules setup
Restoring cache
00:00
Checking cache for master-docker-2...
No URL provided, cache will not be downloaded from shared cache server. Instead a local version of cache will be extracted.
Successfully extracted cache
Downloading artifacts
00:01
Downloading artifacts for docker-hadolint (6121)...
Downloading artifacts from coordinator... ok id=6121 responseStatus=200 OK token=LRUFpXw7
WARNING: reports/hadolint-dde65eefd6c9a71b70c22f15c806082e.json: lchown reports/hadolint-dde65eefd6c9a71b70c22f15c806082e.json: operation not permitted (suppressing repeats)
Downloading artifacts for go-build-test (6122)...
Downloading artifacts from coordinator... ok id=6122 responseStatus=200 OK token=nqXz2-2P
WARNING: bin/: lchown bin/: operation not permitted (suppressing repeats)
Executing "step_script" stage of the job script
00:08
$ # BEGSCRIPT # collapsed multi-line command
[WARN] =======================================================================================================
[WARN] The template docker:1.2.0 you're using is not up-to-date: consider upgrading to version 2.1.1
[WARN] (set $TEMPLATE_CHECK_UPDATE_DISABLED to disable this message)
[WARN] =======================================================================================================
[INFO] Custom CA certificates configured in /kaniko/ssl/certs/ca-certificates.crt
[INFO] Docker authentication configured for
$ run_build_kaniko "$DOCKER_SNAPSHOT_IMAGE" --build-arg http_proxy="$http_proxy" --build-arg https_proxy="$https_proxy" --build-arg no_proxy="$no_proxy"
[INFO] Build & deploy image /snapshot:master
[INFO] Kaniko command: /kaniko/executor --context . --dockerfile ./Dockerfile --destination /snapshot:master --cache --cache-dir=/builds/n8KiyZgX/0/to-be-continuous/tools/tracking/.cache --verbosity info --build-arg CI_PROJECT_URL --build-arg TRACKING_CONFIGURATION --build-arg http_proxy= --build-arg https_proxy= --build-arg no_proxy=
E1013 18:05:11.931688 44 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
error checking push permissions -- make sure you entered the correct tag name, and that you are authenticated correctly, and try again: checking push permission for "/snapshot:master": GET https://index.docker.io/v2/snapshot/blobs/uploads/: UNAUTHORIZED: authentication required; [map[Action:pull Class: Name:snapshot Type:repository]]
Uploading artifacts for failed job
00:01
Uploading artifacts...
WARNING: docker.env: no matching files
ERROR: No files to upload
Cleaning up file based variables
00:00
ERROR: Job failed: command terminated with exit code 1
First of all thanks for your feedback. I thoroughly investigated and you're right: we've recently introduced a bug in our gitlab-sync.sh script that prevented it from recursing :(
A fix is on its way, you should be able to retry it once it's merged.
About your second issue, the logs clearly suggest the hadolint job failed importing your custom CA certificates, but that should not happen using the hadolint/hadolint:latest-alpine image.
See the same job logs on gitlab.com:
[INFO] Custom CA certificates imported in /etc/ssl/certs/ca-certificates.crt
I don't see clearly where the problem could come from.
A few questions to help me investigate:
which kind of GitLab runners did you configure ?
which technique did you use to configure your custom CA certificates ? did you configure a global DEFAULT_CA_CERTS as suggested in our doc ?
is docker-hadolint the only job to fail ? You should also have go-build-test and go-ci-lint on the same stage that also import the custom CA certificates in the same way...

Unable to connect the Botium client with Google DialogFlow

Installed npm via mac terminal.
Installed botium client with npm command : npm install -g botium-cli
As directed in this tutorial :
Also have got allocated one DialogFlow instance and other details with project configuration as directed in the above linked tutorial.
Error I am getting while establishing the connection between botium client and DialogFlow :
Auth error:Error: error:0906D06C:PEM routines:PEM_read_bio:no start
line (node:25129) UnhandledPromiseRejectionWarning: Error: Cannot send
message to dialogflow container: { Error: 14 UNAVAILABLE: Getting
metadata from plugin failed with error: error:0906D06C:PEM
routines:PEM_read_bio:no start line
at Object.exports.createStatusError (/usr/local/lib/node_modules/botium-cli/node_modules/grpc/src/common.js:87:15)
at Object.onReceiveStatus (/usr/local/lib/node_modules/botium-cli/node_modules/grpc/src/client_interceptors.js:1188:28)
at InterceptingListener._callNext (/usr/local/lib/node_modules/botium-cli/node_modules/grpc/src/client_interceptors.js:564:42)
at InterceptingListener.onReceiveStatus (/usr/local/lib/node_modules/botium-cli/node_modules/grpc/src/client_interceptors.js:614:8)
at callback (/usr/local/lib/node_modules/botium-cli/node_modules/grpc/src/client_interceptors.js:841:24)
code: 14, metadata: Metadata { _internal_repr: {} }, details:
'Getting metadata from plugin failed with error: error:0906D06C:PEM
routines:PEM_read_bio:no start line' }
at /usr/local/lib/node_modules/botium-cli/node_modules/botium-connector-dialogflow/dist/botium-connector-dialogflow-cjs.js:222:14
(node:25129) UnhandledPromiseRejectionWarning: Unhandled promise
rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was
not handled with .catch(). (rejection id: 12) (node:25129) [DEP0018]
DeprecationWarning: Unhandled promise rejections are deprecated. In
the future, promise rejections that are not handled will terminate the
Node.js process with a non-zero exit code.
If you need, there is also link to botium client
Can anyone help me here with the connection establishment and get going !
Same error was coming in my case when I was trying to connect botium to dialogue flow.
In my case DIALOGFLOW_PRIVATE_KEY was incorrect. Please check it, if it is starting with
------BEGIN PRIVATE KEY-----
and ends with
\n-----END PRIVATE KEY-----\n
This solved my issue:)