[Release-1.0] Setup Authentication With Apple

[adilanchian]

We currently have Spotify authentication setup and now need Apple. This is required by Apple currently. We also would like to user Apple Music for creating playlists and things of that nature. The current issue with this is there is no "straight forward" way to do this in React Native. We will need to implement some NativeModules to get this thing work. Currently this task should include:

• [x] Authenticate with Apple using Firebase
• [x] Create social platform for user in Firebase
• [x] Create user with Apple creds in Firebase

[adilanchian]

What We Did Today

• Setup dev environment for both Android and iOS

What We Will Do Next Time

• [x] Enable Apple Sign In Button
• [ ] Create Social Platform on AppleAuth

[adilanchian]

What We Did Today

• Setup client to call custom firebase for apple music auth
• Setup Golang template to render html page in browser

What We Will Do Tomorrow

• [x] Continue creating HTML page for authing Apple Music User
• [ ] Get proper token back and create social platform and Firebase user

[adilanchian]

[adilanchian]

What We Did Today

• Continued working on the template in Golang
• Found our new flow of how we are going to handle the Apple Auth (see above)
• Realized we will need to make the "choose username" UI

What We Will Do Tomorrow

• [ ] Setup Getting Apple Developer Token
• [ ] Calling Authorize Service For Apple Music
• [ ] Deep linking back into Grüvee with the access token

[adilanchian]

What We Did Today

• Continued on the track for obtaining a Developer Token. Realized we actually need to create our own JWT
• Pulled in a library to create a JWT in Golang
• Halfway through the implementation of this

What We Will Do Next Time

• [x] Finish creating JWT to call Apple Music API
• [ ] Calling Authorize Service For Apple Music
• [ ] Deep linking back into Grüvee with the access token

[adilanchian]

What We Did Today

• Continued with JWT stuff. WOW so much learnings here haha
• Got the JWT created (almost) ran into signing issue

What We Will Do Next Time

• [x] Convert PrivateKey into proper format
• [x] Send key over to Golang Template
• [ ] AUTH WITH APPLE USER

[adilanchian]

What We Did Today

• Converted PrivateKey from file to proper format
• Sent JWT data over to template
• Also added the ability read JWT token from DB

What We Will Do Next Time

• [x] Fix broken JWT
• [ ] Setup refresh for JWT
• [ ] Create social platform with Apple Auth Token

[adilanchian]

What We Did Today

• Got the deep link stuff working for AppleAuth. This gets the Apple Music MusicUserToken and passes it back to our clients

What We Will Do Next Time

• [ ] Finish setting up the SocialPlatform for Apple Auth
• [ ] Setup refresh for our JWT
• [ ] Create Firebase user for our new Apple Music user

[adilanchian]

NOTE:

Need to add an expiration time on the Apple Music User Token

[adilanchian]

What We Did Today

• Designed a new layout for how we want to create our social Platform, firebase user, and JWT for Apple Dev Token
• Implemented, but not tested, the token generation

What We Will Do Next Time

• [x] Finish setting up the SocialPlatform for Apple Auth
• [x] Setup refresh for our JWT
• [x] Create Firebase user for our new Apple Music user

[adilanchian]

New design for Apple Auth Flow

[adilanchian]

What We Did Today

• Designed new flow for Apple Sign / Apple Music Auth (See above ^)
• Implemented the Apple Sign in portion
• Started to move onto Choose username component

What We Will Do Next Time

• [ ] Create "ChooseUsername" component
• [ ] Add this to the navigation flow for both Spotify and Apple Music

[adilanchian]

At the beginning of trying to setup our new views, the react-native-navigation library was giving us pains again.... It's time to switch to React-Navigation. I think this needs to happen now as the app is still relatively small. Going to do that now before continuing on here.

[adilanchian]

HERE IS THE NEW FLOW:

1. Sign in with Apple ID (Standard, built in flow here)
2. Move onto changing username
3. Once person creates a playlist, prompt messaging saying that Grüvee can create playlists on your behalf! Would you like this?
4. If yes, go through Apple Music sign in else, do nothing!

[adilanchian]

What We Did Today

• We worked on adding logic for Create Username view
• Setup Firebase query to check for usernames
• Currently running into some debounce weirdness

What We Will Do Next Time

• [ ] Finish up create username view
• [ ] Set it up to work with Spotify auth as well
• [ ] Actually create Apple User

[adilanchian]

What We Did Today

• Continued working on the create username view
• Setup the proper logic for button state and showing/hiding availability message
• Realized we need to add a DisplayName field to user doc to properly search for username

What We Will Do Next Time

• [x] Update DB and services to utilize new DisplayName Field
• [x] Lowercase username field
• [x] Add button logic for Apple Auth sign in

[adilanchian]

What We Did Today

• Update DB and services to utilize new DisplayName Field
• Lowercase username field
• Add button logic for Apple Auth sign in
• Ran into some Firestore Rules issues for Apple Sign in

What We Will Do Next Time

• [ ] Fix Firestore rules for Apple Auth
• [ ] Verify Apple User login/logout works
• [ ] Setup Apple Music Sign in flow

[adilanchian]

What We Did Today

• So we ran into a pretty annoying issue with authentication and apple provider today. It looks like it may require us to setup a new db/auth flow for the app. In another comment I am going to post my findings.

What We Will Do Next Time

• [ ] Setup new auth flow kappa.

[adilanchian]

The Issue

When authenticating with a service provider associated with Firebase, a UID is created for us automatically and we can’t change it. That leaves us with issues in our Firebase Rules to go ahead and access certain documents. Since the custom authenticated users have the proper ID’s.

Potential Solution

Create a new collection that maps firebase auth users to their documents. IE: Firebase User UID: 1234567 —> Firebase User Doc {id: apple:999999}

That would mean all our Firebase rules will probably have to change and the way we fetch documents will probably also have to change.

[adilanchian]

What We Did Today

• Today we literally worked on button styling for Apple Auth and Spotify
• It looks SICK and seems to be good to go on both iOS and Android

What We Will Do Next Time

• [ ] Finish up Apple Music flow for getting Apple Music API Token
• [ ] Probably need to get a head start on Firebase rules. BIG YIKES.

[adilanchian]

Apple Music Prompt Flows:

1. When creating playlist, prompt user to auth with Apple Music

   • Send to Golang rendered view
   • Auth
   • Create playlist on users behalf

2. After authing with Apple Music we will need some flag to not prompt the auth again

   • If creating new playlist, we should check this flag
   • If flag is true (saying we have already tried to get user to auth) then don't show prompt and go through proper creation
   • Else show prompt and go through auth if accepted

[adilanchian]

What We Did Today

• Starting setting up Apple Music Auth
• Creating new stack view so we can navigate to Golang Function for Apple Music Auth

What We Will Do Next Time

• [x] Add proper .p8 file back to Golang project
• [x] Get Apple Music Token and store in DB
• [ ] CREATE PLAYLIST IN APPLE MUSIC

[adilanchian]

What We Did Today

• Added the proper .p8 key back into Golang project to create Apple Dev Token
• Changed logic to get Apple Music Token and store in DB!

What We Will Do Next Time

• [x] Stylize our Golang template for getting Apple Music Token
• [x] Do some clean on the flow
• [ ] Create Playlist for Apple Music user on their account

[adilanchian]

What We Did Today

• Fixed up the the Golang Template for our Apple Music Auth (FIRST TRY)
• Cleaned up a lot of the flow for Apple Music Auth in general and it's looking CLEAN
• Started working on adding Apple Music Playlist creation in Golang function

What We Will Do Next Time

• [x] Finish up Golang work for setting up Apple Music API call to create playlist
• [ ] We need to look at the bugs list in our Bear Notes

[adilanchian]

What We Did Today

• We now have Grüvee creating a playlist on an Apple Music account via API (SICK)
• Fixed some issues with our flow on calling creating a social playlist
• Pretty much cleaned up Golang function for creating playlist

What We Will Do Next Time

• [x] Finish up logic for creating a playlist after Apple Music Auth
• [ ] We need to look at the bugs list in our Bear Notes

[adilanchian]

What We Did Today

• Finished up the logic for all the scenarios of adding a playlist after Apple Music auth
• This included updating redux actions and saving playlist name in asyncsStorage

What We Will Do Next Time

• [ ] Fix all the bugs logged in our Bear notes
• [ ] Plan what next steps we need to take for collaboration between Apple Music user and Spotify

[adilanchian]

What We Did Today

• Knocked out 6 bugs that popped during Apple Auth
• Things are looking SWEET.

What We Will Do Next Time

• [ ] We still have two bugs to handle. Let's finish up
• [ ] One of the bugs includes deploying stuff to Firebase. Need to figure out a way to grab versions from a different branch
• [ ] Planning for next feature before beta launch!

[adilanchian]

What We Did Today

• Started fixing issue with our AppleAuth user being null
• Found another bug with Android Deeplinking and sign in
• Looked at the broken song links and no issues so far

What We Will Do Next Time

• [x] Finish up the Spotify Deeplink bug
• [x] Figure out AlgoliaSearch local setup for Firebase Functions
• [ ] Firebase rules
• [ ] Plan next feature to build!

[adilanchian]

What We Did Today

• Fixed Spotify Deeplink Bug (YAY)
• Spent a lot of time trying to get AlgoliaSearch to run locally. Decided to just not worry about it
• Setup PR for ServerSide functions

What We Will Do Tomorrow

• [ ] Finish up PR for Firebase functions
• [ ] Deploy Firebase functions
• [ ] Do a sanity check of functions
• [ ] Setup Firebase Rules

[adilanchian]

(Testing this out in dev first) So some notes:

1. In CreateAppleDevToken function, we need to store our .p8 file in a storage bucket.
2. In our Firebase function we will need to grab these file from our bucket to mint our token
3. Security rule behind this is we should probably just be admin

What We Did Today

• Merged in latest Golang code to backend server
• Deployed new Apple functions into the cloud and realized they are broken
• Started working on adding files to Firebase Storage (.p8 file)

What We Will Do Next Time

• [x] Finish Storage setup for createAppleDevtoken in Dev
• [x] Mimic the same setup in Prod and deploy changes
• [ ] Finalize Firebase Rules

[adilanchian]

What We Did Today

• Finalized Firebase Storage for .p8 file
• Deployed new function with with changes
• Tested out Apple Auth Flow and realized we are now missing AuthTemplate file which may require us to updated this in Storage as well. RIP.

What We Will Do Next Time

• [x] Figure out AuthTemplate file issue
• [x] Deploy changes
• [ ] Firebase Rules
• [ ] TEST AND MOVE ON

[adilanchian]

What We Did Today

• Today we spent the entire stream trying to test our production app
• We had no luck as there seems to be some weird issues with pointing to production from our dev device

What We Will To Next Time

• [ ] Firebase Rules
• [ ] TEST AND MOVE ON

[adilanchian]

All the issues we were having last week with accessing the new functions in prod is like 75% fixed now. I had to move two functions from the client to Firebase Functions as there was no authentication at the point of calling these queries so gotta do em in the cloud! Just have to deal with a few more firebase rules (all the actions for playlists and such).

Then we will need to deploy two more functions to the cloud, update the firebase rules and then we can move on hahaha

[adilanchian]

What We Did Today

• Deployed new Firebase functions
• Tested prod and things are working great!
• Continued on with Firebase Rules (Getting close)

What We Will Do Next Time

• [ ] Finalize Firebase Rules
• [ ] Do a full test pass on prod app version
• [ ] Move onto next feature!

[adilanchian]

What We Did Today

• Worked through some Firebase Rules stuffz
• Still have a bit of logic to figure out here... We started writing a new trigger function that would allow us to link the FB provider logins with user documents, but realized we don't have the request.auth.id to link in the new collection

What We Will Do Next Time

• [x] Look into this new trigger function and see if we can do it through a regular http-request function
• [x] Get these dumb firebase rules done with
• [ ] Move onto next feature

[adilanchian]

What We Did Today

• We re-wrote the trigger function to be just a regular http-request function that is called from the client
• Updated the client to call this when signing in as an Apple user for the first time
• Updated all Firebase Rules (THEY ARE ALL WORKING. POGGERS.)
• Started looking at a potential bug with Apple Music Token Refresh

What We Will Do Next Time

• [x] We need to deploy new Firebase function
• [x] Do full test suite in Prod with Apple Sign in
• [x] Move onto next feature!

[adilanchian]

We are finally done.... WOW.