Cannot get account from appwrite

[ludwing979]

Cannot get account from appwrite

[Aashish1009]

im also getting same issue

[Proj-Valentine]

I am getting the same issue too, cant connect with appwrite

[Proj-Valentine]

When the code in the file config.ts executes this line const currentAccount = await account.get() it does not connect to Appwrite, in the console shows this:

Does anyone have the same issue?

did you get the issue resolved?

[Proj-Valentine]

Yes, I ran into this issue.

I solved it by starting a (1) "web" client, and (2) changing hostname to *

Can step by step run through what you did for it to work?

[IasmimCristina]

@IasmimCristina , Can u please try replacing the
appwriteConfig.databaseId and appwriteConfig.useCollectionId
with the values of those in quotes

Hello!

I have done that, actually, my code was like that but I changed it when I made that screenshot.
(And it was with the double quotes 😢)

The difference it makes is that when the sign in page loads it doesn't get the unauthorized error message.

However, when I reload the page the session doesn't persist still and when I logout I get the unauthorized error message again.

[Rondev9]

@IasmimCristina , Can u please try replacing the
appwriteConfig.databaseId and appwriteConfig.useCollectionId
with the values of those in quotes

Hello!

I have done that, actually, my code was like that but I changed it when I made that screenshot.
(And it was with the double quotes 😢)

The difference it makes is that when the sign in page loads it doesn't get the unauthorized error message.

However, when I reload the page the session doesn't persist still and when I logout I get the unauthorized error message again.

Hey @IasmimCristina, If you don't mind, can you please invite me to your project repo, I'll do my best to resolve the issue.

[Rondev9]

"Fantastic @Onunkwor! 🎉 I'm glad to hear that you resolved the issue. It's always those little details that can make a big difference. Kudos! Also, great catch on fixing the getCurrentUser function—consistent casing is key. If you run into any more challenges or have questions in the future, feel free to reach out. Happy coding! 👩‍💻🚀"

[Rondev9]

@Rondev9 , thank you very much, I invited you just now.

hey! were you able to resolve the issue? i have been facing the same problem for a few hours now and have been unable to tackle it

Hey @siya-pathak, Yeah I'm able to resolve it.

hi could you tell me how did you? i did refer to [https://github.com//issues/19#issuecomment-1807460381](this comment here) and the sign-up is working fine now after making this modification, but i just wanted to know any other way this could be solved :)

You can use local storage to save the user ID, so that it won't complain about the 401 as we're using the user id from local storage whenever we make a call to AppWrite. So why we're using local storage here, overtime AppWrite fails to fetch the user id from AppWrite's session, which results in 401. And don't forget to clear the local storage on sign out.

[siya-pathak]

@Rondev9 , thank you very much, I invited you just now.

hey! were you able to resolve the issue? i have been facing the same problem for a few hours now and have been unable to tackle it

Hey @siya-pathak, Yeah I'm able to resolve it.

hi could you tell me how did you? i did refer to [https://github.com//issues/19#issuecomment-1807460381](this comment here) and the sign-up is working fine now after making this modification, but i just wanted to know any other way this could be solved :)

You can use local storage to save the user ID, so that it won't complain about the 401 as we're using the user id from local storage whenever we make a call to AppWrite. So why we're using local storage here, overtime AppWrite fails to fetch the user id from AppWrite's session, which results in 401. And don't forget to clear the local storage on sign out.

thank you so much for this :)

[hmongdev]

Yes, I ran into this issue.

I solved it by starting a
(1) "web" client, and
(2) changing hostname to *

[ludwing979]

I tried that but still is not working, I also tried to delete the project and create a new one but still is giving me the same error

[hmongdev]

I tried that but still is not working, I also tried to delete the project and create a new one but still is giving me the same error

If your code is 100% correct, it has to be appwrite.

Make sure you set up your auth and database correctly. That's the best advice I can give without looking at your code.

[hmongdev]

I tried that but still is not working, I also tried to delete the project and create a new one but still is giving me the same error

Sorry I haven't had time to write a proper response, but @Rondev9 created it here. These are the steps you must take: #3 (comment)

[hmongdev]

Sorry I haven't had time to write a proper response, but @Rondev9 created it here. These are the steps you must take: #3 (comment)

[hmongdev]

I tried that but still is not working, I also tried to delete the project and create a new one but still is giving me the same error

Sorry I haven't had time to write a proper response, but @Rondev9 created it here. These are the steps you must take: #3 (comment)

[athskouroliakos]

I am dealing with the same issue and creating a web platform did not fix it.

[ludwing979]

When the code in the file config.ts executes this line const currentAccount = await account.get() it does not connect to Appwrite, in the console shows this:

Does anyone have the same issue?

did you get the issue resolved?

No, I search for different solutions but I still can't figure it out

[Rondev9]

When the code in the file config.ts executes this line const currentAccount = await account.get() it does not connect to Appwrite, in the console shows this:

Does anyone have the same issue?

did you get the issue resolved?

No, I search for different solutions but I still can't figure it out

Hey @ludwing979 in order to tackle with the 401, I'm using local storage to store the userId (as a bruteforce method) and on sign out I'm clearing the local storage to delete the current user session.
Here's the reference:

Sign-in:

export async function signInAccount(user: { email: string; password: string }) {
  try {
    const session = await account.createEmailSession(user.email, user.password);
    localStorage.setItem("sessionId", session.userId); //userId stored as a sessionId -> purpose of storing is after some time of user log in, when try to fetch useId on reload the appWrite is unable to fetch resulting 401
    return session;
  } catch (error) {
    console.log(error);
  }
}

Sign-out:

export async function signOutAccount() {
  try {
    localStorage.clear();
    const session = await account.deleteSession("current");
    return session;
  } catch (error) {
    console.log(error);
  }
}

Hope it helps 😊

[athskouroliakos]

When the code in the file config.ts executes this line const currentAccount = await account.get() it does not connect to Appwrite, in the console shows this:

Does anyone have the same issue?

did you get the issue resolved?

No, I search for different solutions but I still can't figure it out

Hey @ludwing979 in order to tackle with the 401, I'm using local storage to store the userId (as a bruteforce method) and on sign out I'm clearing the local storage to delete the current user session. Here's the reference:

Sign-in:

export async function signInAccount(user: { email: string; password: string }) {
  try {
    const session = await account.createEmailSession(user.email, user.password);
    localStorage.setItem("sessionId", session.userId); //userId stored as a sessionId -> purpose of storing is after some time of user log in, when try to fetch useId on reload the appWrite is unable to fetch resulting 401
    return session;
  } catch (error) {
    console.log(error);
  }
}

Sign-out:

export async function signOutAccount() {
  try {
    localStorage.clear();
    const session = await account.deleteSession("current");
    return session;
  } catch (error) {
    console.log(error);
  }
}

Hope it helps 😊

I tried that but the issue remains, the problem as shown in the screenshot seems to be at the getCurrentUser.

[Rondev9]

Hey @athskouroliakos, If it's acceptable to you, kindly add me to your repository. This will allow me to thoroughly study the code, and I assure you that I will contribute towards resolving the error.

[ludwing979]

@Rondev9 Can I also add you to my repository to check, I have the same problem as @athskouroliakos

[Rondev9]

@Rondev9 Can I also add you to my repository to check, I have the same problem as @athskouroliakos

Sure @ludwing979! Please go ahead.

[IasmimCristina]

Were you able to fix it? @athskouroliakos @Rondev9 , I'm facing the same issue.

[TheerthA88]

Were you able to fix it? @athskouroliakos @Rondev9 , I'm facing the same issue.

@IasmimCristina, can you pls share the screenshots if you don't mind

[IasmimCristina]

Here they are:
Im basically receiving the same error as the author of the issue, I've already added the Web platform, and re-made the project in appwrite and checked JSM's code. Weirdly, yesterday it was working fine, but now when I re-load the page the session doesnt work.

The local storage message appears once I login and the first ones as soon as the app loads the signin page.

Here are the functions and console ninja error messages, the same mentioned:

The unathourized error is refering to this line:
const currentAccount = await account.get();

[TheerthA88]

@IasmimCristina , Can u please try replacing the
appwriteConfig.databaseId and appwriteConfig.useCollectionId
with the values of those in quotes

[IasmimCristina]

@Rondev9 , thank you very much, I invited you just now.

[Onunkwor]

I'm having a 401 authorization issue when I try to sign up or sign in. The users are correctly added to app write and the local storage but the page doesn't redirect and I have these issues @Rondev9

[Rondev9]

I'm having a 401 authorization issue when I try to sign up or sign in. The users are correctly added to app write and the local storage but the page doesn't redirect and I have these issues @Rondev9

Hey @Onunkwor, invite me to your project, So that I can understand more about the issue.

[Onunkwor]

@Rondev9 Good morning I've done that

[Onunkwor]

Thank you @Rondev9 I found a solution to it. I added permission to the saveToDb function which worked. I also faced an invalid query error in the getCurrentUser function cos I used [Query.equal("accountId", currentAccount.$id)] instead of [Query.equal("accountID", currentAccount.$id)] because when saving the user to the database I used accountID

[sridhar-pro]

@Onunkwor @Rondev9
I updated the code but still getting same error
can you help me to fix this

[Onunkwor]

@sridhar-pro Good morning, Are you using .env or .env.local for your API keys?

[sridhar-pro]

@Onunkwor i'am using .env.local for the API keys

[Onunkwor]

@sridhar-pro Sorry about the late reply; I've been caught up with schoolwork. I encountered an error where the API keys were not accessed properly when I used .env.local, so I switched to just .env, and it worked fine.

[sridhar-pro]

@Onunkwor thank you brother it's worked

[Onunkwor]

@sridhar-pro you're welcome

[siya-pathak]

@Rondev9 , thank you very much, I invited you just now.

hey! were you able to resolve the issue? i have been facing the same problem for a few hours now and have been unable to tackle it

[Rondev9]

@Rondev9 , thank you very much, I invited you just now.

hey! were you able to resolve the issue? i have been facing the same problem for a few hours now and have been unable to tackle it

Hey @siya-pathak, Yeah I'm able to resolve it.

[siya-pathak]

@Rondev9 , thank you very much, I invited you just now.

hey! were you able to resolve the issue? i have been facing the same problem for a few hours now and have been unable to tackle it

Hey @siya-pathak, Yeah I'm able to resolve it.

hi could you tell me how did you? i did refer to [https://github.com//issues/19#issuecomment-1807460381](this comment here) and the sign-up is working fine now after making this modification, but i just wanted to know any other way this could be solved :)

[Rondev9]

@Rondev9 , thank you very much, I invited you just now.

hey! were you able to resolve the issue? i have been facing the same problem for a few hours now and have been unable to tackle it

Hey @siya-pathak, Yeah I'm able to resolve it.

hi could you tell me how did you? i did refer to [https://github.com//issues/19#issuecomment-1807460381](this comment here) and the sign-up is working fine now after making this modification, but i just wanted to know any other way this could be solved :)

You can use local storage to save the user ID, so that it won't complain about the 401 as we're using the user id from local storage whenever we make a call to AppWrite. So why we're using local storage here, overtime AppWrite fails to fetch the user id from AppWrite's session, which results in 401. And don't forget to clear the local storage on sign out.

thank you so much for this :)

You're welcome @siya-pathak. Happy coding 🚀🚀

[ToufikGouri]

When i am creating a new user, even it gets stored in my DB of appwrite, then still it can't get updated in my redux store, the login and logout is working fine only the Signup is creating problem
Please help me anybody

my userdetails slice looks like this
export const userDetails = createAsyncThunk('userDetails', async () => {
try {
const getData = await account.get()
return getData;
} catch (error) {
return 0
}
})
worked fine with login and logout just problem with the Signup

Sign up function :
e.preventDefault()

    const promise = account.create(
        uuidv4(),
        user.email,
        user.password,
        user.name
    );

    promise.then(
        function (response) {
            console.log(response);
            if (response) {
                dispatch(userDetails()); // Dispatch userDetails action to update the Redux state
            }
            navigate("/")   //Success
        },
        function (error) {
            console.log(error);    //Failed
        }
    )

}


please help meeee

[rahulAgdev]

I faced the same issue, it is because account.get() will not return the current account immediately, which throws the execution to the catch block. And hence you are receiving this error.

To solve this error, I created a separate function to get the current user using the account.get function and then call it inside the getCurrentUser function ( if that is what you have named it )

export async function getAccount() {
  try {
    const currentAccount = await account.get();

    return currentAccount;
  } catch (error) {
    console.log(error);
  }
}

then use this getAccount function to fetch your user account details in your main function.

[ToufikGouri]

I faced the same issue, it is because account.get() will not return the current account immediately, which throws the execution to the catch block. And hence you are receiving this error.

To solve this error, I created a separate function to get the current user using the account.get function and then call it inside the getCurrentUser function ( if that is what you have named it )

export async function getAccount() {
  try {
    const currentAccount = await account.get();

    return currentAccount;
  } catch (error) {
    console.log(error);
  }
}

then use this getAccount function to fetch your user account details in your main function.

But bro as you can see in my starting line of response the code is same as like yours, I used the async await to get user in seperate function :(

[rahulAgdev]

I faced the same issue, it is because account.get() will not return the current account immediately, which throws the execution to the catch block. And hence you are receiving this error.

To solve this error, I created a separate function to get the current user using the account.get function and then call it inside the getCurrentUser function ( if that is what you have named it )

export async function getAccount() {
  try {
    const currentAccount = await account.get();

    return currentAccount;
  } catch (error) {
    console.log(error);
  }
}

then use this getAccount function to fetch your user account details in your main function.

But bro as you can see in my starting line of response the code is same as like yours, I used the async await to get user in seperate function :(

Can you try to call the account.create() function seperately and call it again by returning from another function and try. If this doesn't work, let's connect and debug this together

[bizrockman]

I debugged it a little bit further. Actually this error makes complete sense. And it is not a bug like it was mentioned in the video.

It behaves like intended. You are not logged in so you go to sign-in. As soon as you comment out cookieFallback === null, the method checkAuthUser() is called, but since you are guest (not a logged In user) you do not have an account. So this error occurs.

How this is setup up you will never see the sign-up page.

Now change the line in useEffect to /sign-up.

After you sign-up you will automatically logged In and after you will not get that error any longer.

I did not through with the video, So I do not know how the pageflow will be. But I think that you need some expections while checking the user. If you are not logged In I would redirect you to sign-up. If you click on sign-in you need a further check in useEffect, to ensure that the user stays on sign-in without gettting redirected to sign-up again.

And then you are done ;-)

[bizrockman]

Ok, I have managed it to work correctly with an easy fix:

`const [isAuthenticated, setIsAuthenticated] = useState(false)

const navigate = useNavigate()
const location = useLocation()

const checkAuthUser = async () => {
    setIsLoading(true)
    try {

`

Add const location = userLocation()

and use it in the useEffect Method

` useEffect(() => {
const cookieFallback = localStorage.getItem("cookieFallback");
if (
cookieFallback === "[]" ||
cookieFallback === null ||
cookieFallback === undefined
) {
if (location.pathname === "/sign-in") {
navigate("/sign-in");
} else {
navigate("/sign-up");
}
}

    checkAuthUser();        
  }, []);

`

Now the app is working as expected without the 401 Unauthorized User guest as not account exception

[captaincharan]

@Rondev9 Please help me I am struggling with he issue