Sign in with Google/appple

[kodjima33]

Login with Apple/google

Some people who use iPhones don't have Apple accounts to sign in. They want to
Be able to sign in with Google

[chakri-chax]

Hey there @kodjima33
I wanted to work on this issue
I have good oauth implementation knowledge.

[mdmohsin7]

@chakri-chax we don’t assign or lock bounties to anyone unless they have previously had a PR merged into our repository. If no one is working on an issue, feel free to drop a comment, start working on it, and open a PR.

[ibrahimnd2000]

I am working on it.

[ibrahimnd2000]

Just created a PR for this

[joshijoe05]

/attempt #1769

I have reviewed the codebase and noticed that the sign-in buttons come from different packages, resulting in inconsistencies in their appearance. To maintain a uniform look and avoid dependency on multiple packages, it would be better to create custom buttons that follow a consistent design without affecting the existing code structure

[ibrahimnd2000]

/attempt #1769

I have reviewed the codebase and noticed that the sign-in buttons come from different packages, resulting in inconsistencies in their appearance. To maintain a uniform look and avoid dependency on multiple packages, it would be better to create custom buttons that follow a consistent design without affecting the existing code structure

I addressed this here, it now uses single dependency (sign_in_button) for both of the buttons.

[andrewgazelka]

@addbounty $100

[addbounty]

Make a Draft PR early so others can see you are working on it! To automatically create one:

# Using npx (installed if you have NodeJS/npm)
npx bountybot start BasedHardware/omi#1769

# Or, use cargo (installed if you have Rust)
cargo install bounty
bounty start BasedHardware/omi#1769

When merged, you will receive the bounty!

[beastoin]

Simulator.Screen.Recording.-.iPhone.16.Plus.-.2025-02-16.at.22.01.29.mp4

[kodjima33]

@joshijoe05 can you fix?

@beastoin why did we merge without testing it on a branch first

[beastoin]

fixed it already. bro, we had tested it before merging. but the issue is not happened during testing, it's happened on the production build and is related to the obfuscation.

@kodjima33

[joshijoe05]

fixed it already. bro, we had tested it before merging. but the issue is not happened during testing, it's happened on the production build and is related to the obfuscation.

@kodjima33

So is everything alright now @beastoin ?

[beastoin]

yes /

@joshijoe05 have you try the latest testflight / internal test ver ? and, let me know the good/bad/ugly things. feel free to dm me to get the access.

[joshijoe05]

yes /

@joshijoe05 have you try the latest testflight / internal test ver ? and, let me know the good/bad/ugly things. feel free to dm me to get the access.

Can you send me an invite to this mail ?, will test the new build
Mail : [email protected]

[beastoin]

invitation sent, pls accept it then lmk @joshijoe05

[joshijoe05]

invitation sent, pls accept it then lmk @joshijoe05

I was assigned a Customer Support role, which does not have the necessary permissions to test the latest TestFlight version of the app.

[mdmohsin7]

@joshijoe05 I've invited you to the internal TestFlight group. Please check your email—you should be receiving an invite soon