-
Notifications
You must be signed in to change notification settings - Fork 50
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
Extension fails to upload the binary: uninitialized constant Bundler::Plugin::API::Source #60
Comments
Hi @Jossif. It appears this was an issue with bundler (rubygems/bundler#5488) that has apparently been fixed (although I don't see a release with the fix). That thread indicates that version 1.13.4 should still work. As an aside, which task was causing the error? I don't believe the tasks install bundler so I'm trying to understand what your build process is. Are you managing the bundler installation and then trying to run a build with this extension installed? |
I can report the same issue with my App Store Build task, using only the task defaults. It's grabbing the bad bundler version during the fastlane gem install, so this will probably affect everybody until the aforementioned fix is released. I couldn't find a way to override the bundler/fastlane version -- is there one?
|
Unfortunately, at this time, there isn't a way to override the fastlane version. However, I'm currently working on a PR that will allow it. Furthermore, it will allow you to decide whether you even want the fastlane tools installed at all. |
I just merged the PR that allows making fastlane installation optional (as well as allowing you to choose a particular version). The README has also been updated. The marketplace has the new version so it should now be available to you. Please try it out and let us know if you see any issues. Thanks! |
The manual version selection works like a charm! Unfortunately, I couldn't get it to solve this particular issue, as the bad bundler version (1.14.4) is still being used no matter which fastlane version is selected. I even tried going all the way back to fastlane 1.92.0, which was the most recent version that doesn't reference bundler (at least as a runtime dependency), and it still invoked bundler 1.14.4 (and this is even though 1.14.6 is the latest released version). This is using a VSTS hosted build agent -- is there a cached toolkit on those maybe? I was trying to figure out how to run "gem install bundler" prior to the fastlane task to see if it might update to 1.14.6, but no luck so far.
|
OK. I see what's happening there. Even though the version of fastlane you requested to be installed is being installed (at least, reported to be installed), it is still using 2.19.1 (see the fifth log line up from the bottom). So that's why it's still calling bundler. It appears that you'll need to uninstall that version of fastlane (2.19.1) before we can go back to a previous version. There's some detail about how to do this here. I'll have a look to see if it makes sense to add this capability to the task (and, if so, how). Thanks for trying it out and reporting back! |
Hi @josephayoung and @Jossif. I see that a new version of bundler with the fix has been released. However, as I see it, it appears that even if we install a later version of fastlane, as long as the bundler dependency is fulfilled (a version of bundler that's in the range that fastlane requires is present locally), bundler won't be updated. For instance, I had bundler 1.13.7 and installed the latest version of fastlane. fastlane was just fine with that version of bundler (even though it might have had this particular error). Only until I had uninstalled bundler did it get updated when I installed a later version of fastlane. Although I can add functionality to the task to uninstall a version (or all versions) of fastlane, unless the bug is in fastlane itself, it wouldn't protect this particular issue type. In that case, you'd still need access to the build machine to remove the bad bundler, and then reinstall fastlane. And if you're on the build machine to remove the bad bundler, you may as well install the version of fastlane you want as well. |
I've tried with different bundler versions:
bundler-1.14.5, bundler-1.14.3
The text was updated successfully, but these errors were encountered: