Fixing Token Decoding Issue #61

[rparker2003]

Closes #61

Description / Changes Made

• The JWT tokens now created and passed from the frontend have a "Bearer" prefix and use the field "sub" instead of "uid".
• I modified line 57 to split the string on spaces and take only the 1st index value as this is the actual token we want.
• I modified line 68 to retrieve the "sub" field of the decoded token as the "uid" field is now invalid with the way JWT tokens are passed.

How to Test

1. Add following code into frontend/app/(tabs)/index.tsx at the top of the export function Index():

   const { getToken } = useAuth();
   
   useEffect(() => {
   (async () => {
     const token = await getToken();
     console.log(token);
   })();
   }, []);

   You must also add the respective imports for the above code:

   import { useAuth } from '@clerk/clerk-expo';
   import { useEffect } from 'react';

2. Start the front end, and after logging in through the profile page, you will see the JWT token logged to the console.
3. Add the prefix "Bearer " to the newly created JWT token in the Authentication header in Postman, and test any routes.
4. (Optional) You can put the newly created JWT token in to https://jwt.io to verify the JWT token has a "sub" field instead of a "uid" field.

Checklist

• [ x ] I have added/updated relevant documentation, and I have followed the coding style guidelines.
• [ x ] I have checked for any potential conflicts with other branches and fixed any merge conflicts.
• [ x ] I have verified that a newly created JWT token with the proper "Bearer" prefix in the Authentication header decodes as expected.