# Problem with Google auth due to bundle install

**URL:** <https://meta.discourse.org/t/problem-with-google-auth-due-to-bundle-install/340475>\
**Category:** Development\
**Tags:** unsupported-install\
**Created:** [December 4, 2024, 8:56pm UTC](https://meta.discourse.org/t/problem-with-google-auth-due-to-bundle-install/340475 "2024-12-04T20:56:13Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [December 6, 2024, 1:47am UTC](https://meta.discourse.org/t/problem-with-google-auth-due-to-bundle-install/340475/8 "2024-12-06T01:47:54Z")

</div>

Wow! You noticed the version!

That’s it! (maybe)

I did an apt update to install some stuff (vim but especially tiny\_tds for the import. So maybe something that I upgraded forced am upgrade of omniauth.

No. That’s not it. I removed the Gemfile.lock so when i did the bundle install, it upgraded omniauth?

So maybe rather then this being an annoyance, it might really help find an issue with the new omniauth.

I’ll see it I can replicate it, maybe by just upgrading omniauth. Maybe just delete the Gemfile lock and bundling?

Oh. Maybe this is why setting IMPORT=1 is more important than I thought.

Edit: yes. It definitely must be about doing a bundle install to add the tiny\_tds for the import. I often don’t use IMPORT=1 because it causes other problems. I’ll try to confirm that it’s the Omni auth upgrade that’s causing the problem, but it seems very likely

---

_[View the full topic](https://meta.discourse.org/t/problem-with-google-auth-due-to-bundle-install/340475)._