P12 "File does not exist"

I’m using the CLI to create an iOS build, an opted to provide my own certificate. At one step it asks for the path of my p12 file. When I give it the path it says “File does not exist.” I’ve tried endless options, including dragging the p12 file from Finder to the Terminal, so the path is automatically populated.

Seems like the build process is broken when you try to supply your own p12 file.

1 Like

this certainly works for other folks and i’m personally not familiar with this so i can’t help too much unfortunately, but i’ve pinged @edgar on this and he may be able to help when he’s around

Not sure if this matters, but I previously built successfully when I had
the CLI create my certificate for me. At some point the build process
stopped working, telling me to use the “-c” command. So I did, but it kept
failing, telling me to use the “-c” command. So now I’m trying it with
supplying my own certificate and getting the error about the File not
existing.

@edgar @skevy - please help @thenewt15 :open_mouth:

hi, can you copy paste the exact commands that are given and the version of the exp CLI tool?

Tried with both 46.0.5 and 46.0.6.

I run exp build:ios -c
It asks for my login information, which I provide.
It asks whether I want to provide my own p12 file. I do.
The prompt says “Path to p12 file”.
I enter a path, it returns “File does not exist”

okay, what kind of path are you giving? Absolute? Relative? With ~? Are you entirely sure that the file does not exist?

1 Like

I’ve tried all three:

/Users/me/Desktop/cert.p12
~/Desktop/cert.p12
…/…/Desktop/cert.p12

The file is definitely there. I can drag it straight from finder to populate the path for me in the CLI tool. When I do that, it uses the first path I listed.

1 Like

I also face the same issue.
the cmd running in Desktop also the p.p12 file is in the Desktop [Mac OSX high seria]
I tried it all with ~/User/xxx/Desktop/p.p12, /User/xxx/Desktop/p.p12, p.p12

but no luck.

2 Likes

I have the same problem. Android keystore file path too…

Hey everyone, this issue should be fixed now in the latest version of exp (v47.0.0). Let me know, if you’re still having this problem after upgrading!

2 Likes

hello fson,

I’m still having this issue. I use v47.1.4 and there is no way to make exp convince there is p12 file. I’ve tried to write, nope. I’ve tried to drag file to terminal, big nope! what should I do?

I am also having trouble finding my p12 file

Hi, replied in other post.

if anyone having this problem now then here is the solution

Do not drag and drop a file to the terminal.

add the path from your home

~/dev/folder/file.p12

~/ is important to start from Home

sure if this matters, but I previously built successfully when I had
the CLI create my certificate for me. At some point the build process
stopped working, Click Here Click Here telling me to use the “-c” command. So I did, but it kept
failing, telling me to use the “-c” command. So now I’m trying it with
supplying my own certi

Hey,
I am still having this issue.
In my case, I am trying expo upload:android with the JSON key file.

@smashreality I did also try your suggestion, however it didn’t work it still says “File doesn’t exist”.

Hey fson,
I am still experiencing this issue with the android JSON key.

My expo diagnostics are:

Expo CLI 3.0.10 environment info:
System:
OS: macOS 10.14.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.9.0 - ~/.nvm/versions/node/v12.9.0/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.10.2 - ~/.nvm/versions/node/v12.9.0/bin/npm
IDEs:
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
expo: ^34.0.1 => 34.0.4
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
npmGlobalPackages:
expo-cli: 3.0.10

I have tried to drag-and-drop the file path as well as typing it.
(the file path doesn’t contain spaces or special characters…)

I hope you can help me thank you in advance.

FYI I ran into this today despite dragging and dropping my file into terminal but found the solution:

Turns out the issue was that after dragging, the path automatically had a space at the end. Once deleted, it worked.

(It may be a good idea for the CLI to trim whitespace from the path for this reason, but I’ll leave this up to the maintainers to determine since they have a lot on their plate…!)