Comments (21)
I was having this error, but it turned out to be a problem with the itunes account i was using. It worked perfectly when I used the main itunes connect account, so it seems that there is some permissions thing that was missing.
from boarding.
I had similar problem, and changing to the main account resolved this issue for me too.
But I'm a bit disappointed that I have to disclose credentials for account that has some other released applications.
from boarding.
I have the same problem. Nothing works unless I grant admin rights to the user, specified in the app configuration. I'll try to fix it this weekend and send you pull request.
PS. Just small observation - regardless of admin rights, I always get this error in the log, so seems like this error messages is not related to the root cause of failure :)
from boarding.
Same issue here, using an iTunes Connect 'technical' account;
Going to create a new tester: [email protected] - Ben Collier
2015-12-11T13:38:30.442709+00:00 app[web.1]: F, [2015-12-11T13:38:30.442394 #3] FATAL -- : #<Spaceship::Client::UnexpectedResponse: {"data"=>nil, "messages"=>{"warn"=>nil, "info"=>nil, "error"=>["Forbidden"]}, "statusCode"=>"ERROR"}>
2015-12-11T13:38:30.442710+00:00 app[web.1]: F, [2015-12-11T13:38:30.442600 #3] FATAL -- : /app/vendor/bundle/ruby/2.2.0/gems/spaceship-0.15.1/lib/spaceship/client.rb:263:in `parse_response'
No 2FA enabled.
from boarding.
Same issue using an 'App Manager' account. Would prefer not to have to use the main account for this
from boarding.
You'll need to update spaceship
to the latest version. Please follow the update guide on the README to update to the latest spaceship
from boarding.
I installed a fresh version about 8 hours ago, has there been changes since then?
[edit] Ah, I see, will give that a try, thanks!
from boarding.
Deleted the boarding app from heroku
Installed it from scratch
Expected that spaceship dependency will be resolved to the latest version (as we can see 0.19.0 in logs - it happened)
Checked.
Still I experience the same behavior as before.
2016-01-05T11:19:27.866158+00:00 app[web.1]: I, [2016-01-05T11:17:12.432924 #3] INFO -- : Completed 200 OK in 3ms (Views: 2.9ms)
2016-01-05T11:19:27.866170+00:00 app[web.1]: I, [2016-01-05T11:19:25.939892 #3] INFO -- : Processing by InviteController#submit as HTML
2016-01-05T11:19:27.866176+00:00 app[web.1]: F, [2016-01-05T11:19:27.866066 #3] FATAL -- : /app/vendor/bundle/ruby/2.2.0/gems/spaceship-0.19.0/lib/spaceship/client.rb:268:in `parse_response'
2016-01-05T11:19:27.866177+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/spaceship-0.19.0/lib/spaceship/tunes/tunes_client.rb:693:in `testers'
2016-01-05T11:19:27.866180+00:00 app[web.1]: /app/app/controllers/invite_controller.rb:58:in `submit'
2016-01-05T11:19:27.866182+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
2016-01-05T11:19:27.866183+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
2016-01-05T11:19:27.866184+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
2016-01-05T11:19:27.866185+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
2016-01-05T11:19:27.866186+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
2016-01-05T11:19:27.866187+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:505:in `call'
2016-01-05T11:19:27.866187+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:92:in `_run_callbacks'
2016-01-05T11:19:27.866189+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:81:in `run_callbacks'
2016-01-05T11:19:27.866189+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
2016-01-05T11:19:27.866190+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
2016-01-05T11:19:27.866192+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/notifications.rb:164:in `block in instrument'
2016-01-05T11:19:27.866193+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
2016-01-05T11:19:27.866199+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
2016-01-05T11:19:27.866201+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/abstract_controller/base.rb:137:in `process'
2016-01-05T11:19:27.866202+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionview-4.2.1/lib/action_view/rendering.rb:30:in `process'
2016-01-05T11:19:27.866203+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_controller/metal.rb:196:in `dispatch'
2016-01-05T11:19:27.866204+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
2016-01-05T11:19:27.866207+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:43:in `serve'
2016-01-05T11:19:27.866208+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/journey/router.rb:30:in `each'
2016-01-05T11:19:27.866209+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/journey/router.rb:30:in `serve'
2016-01-05T11:19:27.866210+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/routing/route_set.rb:819:in `call'
2016-01-05T11:19:27.866212+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/etag.rb:24:in `call'
2016-01-05T11:19:27.866212+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:38:in `call'
2016-01-05T11:19:27.866216+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
2016-01-05T11:19:27.866223+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
2016-01-05T11:19:27.866233+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
2016-01-05T11:19:27.866234+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.1/lib/rails/engine.rb:518:in `call'
2016-01-05T11:19:27.866234+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.1/lib/rails/application.rb:164:in `call'
2016-01-05T11:19:27.866237+00:00 app[web.1]: /app/vendor/ruby-2.2.3/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
2016-01-05T11:19:27.866228+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
2016-01-05T11:19:27.866228+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/middleware/static.rb:113:in `call'
2016-01-05T11:19:27.866233+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
2016-01-05T11:19:27.866234+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.1/lib/rails/application.rb:164:in `call'
2016-01-05T11:19:27.866235+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/lock.rb:17:in `call'
2016-01-05T11:19:27.866238+00:00 app[web.1]: /app/vendor/ruby-2.2.3/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
2016-01-05T11:19:27.866239+00:00 app[web.1]: /app/vendor/ruby-2.2.3/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'
2016-01-05T11:19:27.866228+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
2016-01-05T11:19:27.866228+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.1/lib/action_dispatch/middleware/static.rb:113:in `call'
2016-01-05T11:19:27.866234+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.1/lib/rails/engine.rb:518:in `call'
2016-01-05T11:19:27.866235+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/lock.rb:17:in `call'
2016-01-05T11:19:27.866236+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/content_length.rb:15:in `call'
2016-01-05T11:19:27.866237+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/handler/webrick.rb:88:in `service'
2016-01-05T11:19:27.866238+00:00 app[web.1]: /app/vendor/ruby-2.2.3/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
2016-01-05T11:19:27.866228+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
2016-01-05T11:19:27.866233+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
2016-01-05T11:19:27.866235+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/lock.rb:17:in `call'
2016-01-05T11:19:27.866237+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/handler/webrick.rb:88:in `service'
2016-01-05T11:19:27.866238+00:00 app[web.1]: /app/vendor/ruby-2.2.3/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
from boarding.
^ Any idea @KrauseFx?
from boarding.
Make sure to use the latest version of spaceship
0.19.1
from boarding.
This still doesn't work @KrauseFx
- Installing from scratch still results in spaceship 0.19.0 being installed, I guess since the
Gemfile.lock
specifies that version - Even after manually updating to the latest (now
0.19.3
) I get the same error when using an account that is an App Manager for the app in question
Any ideas?
from boarding.
I just pushed 82415d3, could you try that? 👍
from boarding.
I just install it (with spaceship 0.19.3 as you did in @82415d3), and it returns me same error with an specific account for that :(
from boarding.
Any update on this? Am getting the same issue when signing up on heroku boarding app. The ITC account who created the app is an admin and I am definitely using the newest version of spaceship. @KrauseFx
from boarding.
I'm experiencing this bug with a fresh install of boarding - trying to use a non-admin account with "app manager" permissions. The signup form appears fine, but when you submit it gives an error.
from boarding.
@Draknek boarding only supports Admin accounts currently
from boarding.
@KrauseFx Why is that? App manager accounts should have the required permissions I think, and it's reasonable to not want to share login credentials for an admin account.
I'm happy to take a look at the code if this might be a fixable problem?
from boarding.
@Draknek Yes, agreed. Feel free to dive into the spaceship code. One of the requests (I think listTeam
) requires admin privileges, so that's why spaceship fails.
Your role is App Manager, and boarding doesn't work, right? If you don't get it to work, let me know, I might be able to look into this over the next few days/weeks 👍
from boarding.
Okay thanks. I'm not familiar with the codebase but I'll dive in and see if I manage to get anywhere.
And yeah, this is definitely related to roles: with the App Manager role boarding doesn't work, but with an admin role it does.
from boarding.
This should work now, #150 was merged a little while ago to enable App Manager
to be used along with Admin
from boarding.
Closing this because of fix ^ 😊
from boarding.
Related Issues (20)
- Question - Can I use boarding to add users to the App Store Connect Users group
- Supporting 2FA as of 29th Feb HOT 2
- Support for bulk adding participants HOT 1
- Email already registered error shown, but user still added to correct group
- If no default external group added, user is still added to All Users
- No favicon in tab
- How to update to a new version?
- How to deploy to Heroku with 2-factor? HOT 6
- HTTP ERROR 410 Gone HOT 5
- Fastlane update to 2.120 HOT 6
- A new tester doesn't get added to TestFlight HOT 5
- Something went wrong, please contact the application owner. HOT 4
- Vanilla deployment to Heroku fails HOT 4
- Move to JWT authentication
- bundler 2.0.1 issue HOT 9
- Spaceship::UnauthorizedAccessError: Unauthorized Access thrown 8 hours after deployment HOT 3
- fastlane
- fastlane/boarding/TestFlight
- fastlane/boarding/testflight
- Heroku InviteController#index is missing a template
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from boarding.