Hi, I am trying to opt into google’s-play signing using the following command:
expo opt-in-google-play-signing
I follow the prompts, provide the key. the process eventually stops when it fails to install
node-pty-prebuilt
I tried installing the lib independently but failed, also tried installing older versions. I looked into their repo’s issues and got really discouraged. There are similar installation issues opened and w/o resolution. Doesn’t look like its being properly maintained.
I’m experiencing a similar issue as fozzarelo. The process continues to fail on the install of the npm package and I can’t install the library manually.
theylooksotired is on expo32. I don’t think it’s a good idea to go back to 32 for many reasons. But the most relevant for this topic is that it won’t build 64bit.
For now, I would recommend staying on 33 and a recent cli but don’t use the ‘–type app-bundle’ option when building. This will give you a good old fashioned signed-apk on 64bit covering the August requirement.
No doubt Google will be requiring aabs soon, but not yet. And I am sure Expo’s team will have this solved by then.
charliecruzan As you can see I made a couple of assumptions here and there even ventured out a recommendation. Please correct me if I’m wrong.
thanks @charliecruzan:
Won’t that bring compatibility issues? I’m pretty sure I had to go to Node12 when I upgraded my cli.
I’ll double check in the afternoon and report back.
@fanofskynyrd
I didn’t solve it. Not a blocker for me so I moved on.
The august requirement was 64 bit, and that can be met without the --type app-bundle.
I’m sure i’ll have to to revisit this soon.
Till then…