Hi, I am trying to install a Custom iOS Expo Client on my iPhone. When I click “Tap to Install” on the expo build page, it says:
(“null)” is Already Installed
“(null)” has the same Bundle ID as “(null)” and can’t be installed. To continue, delete “(null)” from your device and try again.
I found this thread on apple discussions, but I don’t see any unnamed app on my app list. This post suggests setting legacy build mode, and I don’t know if that is possible with expo.
Thanks for any help!
expo diagnostics
Expo CLI 3.21.5 environment info:
System:
OS: Linux 5.3 Ubuntu 19.10 (Eoan Ermine)
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 12.18.0 - /usr/bin/node
Yarn: 1.22.4 - /usr/bin/yarn
npm: 6.11.2 - /usr/local/bin/npm
npmPackages:
expo: ~37.0.3 => 37.0.12
react: ~16.9.0 => 16.9.0
react-dom: ~16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ~0.11.7 => 0.11.7
1 Like
Same issue, thanks for any advice.
Expo CLI 3.18.0 environment info:
System:
OS: macOS 10.15.4
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 13.12.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.4 - /usr/local/bin/npm
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6392135
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
npmPackages:
expo: ^37.0.0 => 37.0.10
react: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
npmGlobalPackages:
expo-cli: 3.18.0
1 Like
agucho
June 18, 2020, 4:06pm
3
Same here. Did you guys make it work?
Expo CLI 3.20.9 environment info:
System:
OS: macOS Mojave 10.14.5
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.16.3 - ~/.nvm/versions/node/v12.16.3/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.4 - ~/.nvm/versions/node/v12.16.3/bin/npm
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5900203
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmPackages:
expo: ^37.0.0 => 37.0.11
react: 16.9.0 => 16.9.0
react-dom: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ^0.11.7 => 0.11.7
react-navigation: ^4.0.10 => 4.3.9
npmGlobalPackages:
expo-cli: 3.21.5
rhawkins:
expo diagnostics
Having the same issue
Expo CLI 3.20.9 environment info:
System:
OS: macOS 10.15.4
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
npm: 6.13.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
IDEs:
Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
npmPackages:
expo: ~37.0.3 => 37.0.12
react: ~16.9.0 => 16.9.0
react-dom: ~16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ~0.11.7 => 0.11.7
BTW this is the screenshot of the error message:
In addition to this thread I opened an issue on expo-cli github repo:
opened 08:17AM - 19 Jun 20 UTC
closed 05:18PM - 24 Jun 20 UTC
## Description
I am trying to install a Custom iOS Expo Client on my iPhone. Wh… en I click “Tap to Install” on the expo build page, it says:
```
(“null)” is Already Installed
“(null)” has the same Bundle ID as “(null)” and can’t be installed. To continue, delete “(null)” from your device and try again.
```
## Expected Behavior
```
expo client:ios
```
After the complete build I would expect if clicking the `Tab to Install` button the Clustom iOS Expo Client would be installed.
## Observed Behavior
After the successful build I pressed the `Tab to Install` button what opens the Error message:
```
(“null)” is Already Installed
“(null)” has the same Bundle ID as “(null)” and can’t be installed. To continue, delete “(null)” from your device and try again.
```
## Environment
```
# expo diagnostics
Expo CLI 3.21.5 environment info:
System:
OS: macOS 10.15.4
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 13.12.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.5 - /usr/local/bin/npm
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6392135
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
npmPackages:
expo: ^37.0.0 => 37.0.10
react: 16.9.0 => 16.9.0
react-dom: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ^0.11.7 => 0.11.7
npmGlobalPackages:
expo-cli: 3.21.5
```
```
# sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.4
BuildVersion: 19E287
```
## Reproducible Demo
using the following app.json
```
{
"expo": {
"name": "MyApp",
"slug": "myapp",
"platforms": [
"ios"
],
"version": "1.0.0",
"orientation": "portrait",
"icon": "./assets/images/icon.png",
"scheme": "myapp",
"splash": {
"image": "./assets/images/splash.png",
"resizeMode": "contain",
"backgroundColor": "#ffffff"
},
"updates": {
"fallbackToCacheTimeout": 0
},
"assetBundlePatterns": [
"**/*"
],
"ios": {
"bundleIdentifier": "com.domain.myapp",
"buildNumber": "1.0.0",
"supportsTablet": true,
"infoPlist": {
"UIBackgroundModes": [
"location",
"fetch"
]
}
},
"packagerOpts": {
"config": "metro.config.js",
"sourceExts": [
"js",
"jsx",
"svg",
"ts",
"tsx"
]
}
}
}
```
And run the following commands:
```
expo publish
expo client:ios
```
After build is finished press the `Tab to install` button and you get the error:
![IMG_E9482BBEEADC-1](https://user-images.githubusercontent.com/5663605/85112532-0c15c780-b216-11ea-9e6b-7c29ba6a2183.jpg)
Any comments or advices are warmly welcome…
Same issue here. A workaround is to download the .ipa from the Build Details page and manually install it through iTunes.
Good tip, however I have a 2011 Mac that can’t do this (my dev machine is Linux). Thank you for opening an issue, @dameyerdave
Same issue, here. The web page doesn’t appear to have a build details part either, so I can’t seem to download for the workaround. @mgronblad
The build dashboard does not reflect the expo-client.
This same error shows up even after deleting the existing Expo app from my device.
Can anyone having this issue share their app.json
file here?
Edit: nvm, was able to find one in the linked github issue
{
"expo": {
"name": "ABC",
"slug": "abc",
"privacy": "public",
"platforms": ["ios", "android"],
"version": "0.0.6",
"orientation": "portrait",
"icon": "./assets/icon.png",
"splash": {
"image": "./assets/splash.png",
"resizeMode": "contain",
"backgroundColor": "#ffffff"
},
"updates": {
"fallbackToCacheTimeout": 0
},
"assetBundlePatterns": ["**/*"],
"ios": {
"supportsTablet": false,
"bundleIdentifier": "my.build.identider",
"buildNumber": "0.0.6"
},
"facebookScheme": "fb123456",
"facebookAppId": "123456",
"facebookDisplayName": "foobar"
}
}
Here is the build if it helps
https://expo.io/client/wMFVcNWwyWausywFhGWbxr
@charliecruzan thanks for looking into this! Greatly appreciated! This is currently blocking our development for our latest update, so if there is any way I can help speed up the process, please let me know! I appreciate such an amazing project you and your team have made!
ax0n
June 22, 2020, 8:58pm
13
This sounds like a viable route but I don’t see the option to download on the webpage anymore. did you do this from your computer?
ax0n
June 22, 2020, 9:02pm
14
Same Issue. Here is my expo diagnostics output also.
❯ expo diagnostics
Expo CLI 3.21.9 environment info:
System:
OS: macOS 10.15.5
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
Yarn: 1.22.4 - ~/.nvm/versions/node/v13.13.0/bin/yarn
npm: 6.14.5 - ~/.nvm/versions/node/v14.4.0/bin/npm
IDEs:
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
npmPackages:
expo: ^37.0.0 => 37.0.12
react: 16.9.0 => 16.9.0
react-dom: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ^0.11.7 => 0.11.7
react-navigation: ^4.3.9 => 4.3.9
and a screenshot…
cheers
I couldn’t find this option eather…
Thanks everyone for your patience and for reporting this, we’ve discovered the root cause and a fix should be deployed soon (will update here once it is)
Hello again everyone- this should be fixed in production now, and doesn’t even require an expo-cli
update! Let me know if you are still seeing the issue
1 Like
ax0n
June 25, 2020, 2:48pm
18
testing now - will post as soon as I can confirm. Thanks @charliecruzan !
ax0n
June 25, 2020, 3:07pm
19
Working now. Thanks again.
system
Closed
July 15, 2020, 3:07pm
20
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.