-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI for mobile deployment #2954
CI for mobile deployment #2954
Conversation
6ca5a53
to
60b7fcc
Compare
60b7fcc
to
5499a59
Compare
5499a59
to
11fdb3e
Compare
11fdb3e
to
deeb92f
Compare
deeb92f
to
6f9409f
Compare
6f9409f
to
2c529af
Compare
2c529af
to
bb9252b
Compare
I don't know why it says a user is required:
I tried deleting the existing token and made a new one, in case that matters. |
I'm looking into it, not sure why it's not working. It should technically base on the docs. |
Is it somehow not happy because my expo account and this repo aren't for the same user? |
Not sure. I'm doing some testing in my other side project to see. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still doesn't work. I'd file an issue with them, or see if you can ask for advice. It has to be the org vs. username on the token.
bb9252b
to
6b929a7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few things and we can land this.
6b929a7
to
7e2b922
Compare
Issue This PR Addresses
Fixes: #2732
Type of Change
Description
For testing CI purposes I'm also set up to publish on PR creation, but I think it's better to only publish once we push to master
Steps to test the PR
Checklist