-
I'm on a free account within the trial period. Within my flutter build workflow, I am able to successfully login using the generated CI token. However, when I run Here's my step:
Here's some logs from the action:
All of this works seamlessly locally. Am I missing something here? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
can you provide a copy of your pubspec.yaml. The case of your package name 'APP_PACKAGE' looks suspect as package names are normally lower case. Do you have a macro/environment var called 'APP_PACKAGE' which hasn't expanded correctly? |
Beta Was this translation helpful? Give feedback.
-
I've just checked and there is no package called 'APP_PACKAGE' that has been uploaded to onepub, so your package name is incorrect. |
Beta Was this translation helpful? Give feedback.
-
OK, apologies, I should have guessed that you had redacted the package. So the problem is that you have created a team 'betr' and associated the package with that team. You CI/CD account however is not a member of the' betr' team. Go into OnePub | Members, Any problems let me know. |
Beta Was this translation helpful? Give feedback.
OK, apologies, I should have guessed that you had redacted the package.
So the problem is that you have created a team 'betr' and associated the package with that team.
You CI/CD account however is not a member of the' betr' team.
Go into OnePub | Members,
find the CI/CD member
Click the 'Teams' tab
And the click the checkbox next to the 'betr' team.
Click save.
The CI/CD role should now have access to the package.
Any problems let me know.