The setup of Supabase and its login issue

[Amazingren]

Dear @ShahabEJ ,

I hope you are doing great and thank you for sharing this amazing work!

When I tried to set the chat2geo and wanted to play with it, it seemed there were some problems during the Supabase setup.

Specifically, I copied the URL and project API keys from the webpage below:

However, when I tried to log in after running npm run dev. It always shows the error below (Error: Invalid login credentials):

I double-checked the email and the pwd, they are correct since I can use the email and the corresponding pwd login on the Supabase website.

To this end, I am just wondering if there is something wrong with the setup of Supabase from me.

I am looking forward to hearing from you and thank you in advance for your help.

With warm regards,

[ShahabEJ]

@Amazingren, did you set up the auth table on Supabase? The credentials that you need to put into the login page in the app should be set in the auth table?

[Amazingren]

@Amazingren, did you set up the auth table on Supabase? The credentials that you need to put into the login page in the app should be set in the auth table?

Hi @ShahabEJ, thanks for the reply, you are right, after I added test users in the auth table, now it looks like:

However, here are other two issues:

• When I try to select a polygon area to analyze, there is no button named finalize_roi as you showed in the demo video.

• When I tried to just say hello in the chat, it showed me:

I'm sorry for disturbing you with these maybe too-easy questions, but they bothered me a lot. It would really helpful to hearing more suggestions from you.

Bests and many thanks,

[Amazingren]

I realized it may caused by the database, then I copied the updated schema.sql to the SQL Editor of Supabase, and now it shows:

Also, do you gave any idea regarding this?

[ShahabEJ]

@Amazingren,

1. For ROI drawing, you need to open it through the "Toolbox":

2. For the problem regarding not seeing your usage and chat not working, please refer to How to allocate ressources #6 (comment)

3. For the DB issue, I just updated the schema, which should solve this problem! It's one of those weird things! sorry for that.

Also, check out the readme again as I'll update it in a moment. There is another env variable I missed to put there (BASE_URL).

[Amazingren]

@ShahabEJ Thank you so much for your patience regarding my questions.

Now the ROI selection problem is solved, and the rest seems to be all related to the setup of the DB issue.

• I tried to directly copy everything from your latest updated schema.sql, and then paste them directly into the SQL Editor. However, it shows the below error again:

meanwhile, I also followed some suggestions from the Assistant, it seems still not working for me.

• Additionally, I directly copied the schema provided via How to allocate ressources #6 (comment), here. but it shows me some other issues:

Based on previous tries, I would like:
Q1: Am I correct to set up the DB by directly copying the schema provided by you into the SQL Editor and run? Or I might miss some steps to set it up.

Q2: Regarding the user_roles and user_usage , I didn't find any buttons about these, is this require the schema.sql successfully run?

I am looking forward to hearing more suggestions from you.

Best regards and many thanks,

[ShahabEJ]

@Amazingren, I'll do my best to make sure you can run the app.

For the DB, please first delete any tables you have in your DB. Then, use the latest version of the db-schema and run it in the Supabase SQL editor. I just tested it and it worked for me.

For Q2, I added a new trigger to the db schema so when a new user is added to the auth table, they'll be automatically added to the user_roles table (and then to the user_usage table).

With these, you should be able to fix this issue.

Let me know if you still face any issues with it.

[Amazingren]

Hi @ShahabEJ, again, thank you so much for your very detailed instructions and efforts. I really appreciate it! :)

After I tried again. Below are some update:

1. Feedback:

• Regarding the schema, following your suggestion, I deleted the entire project in Supabase and recreated a new one. Then I copied the new schema in the SQL Editor, and it showed me this (seems ):

• Regarding the tables, after I ran the updated schema, I got tables like these:

(1. lots of tables are created. 2. The `user_usage` and `user_role` are all empty.)

2. Problem:

• 2.1 I first manually add user -> create new user button by providing the email and a pwd.
• 2.2 Then I run npm run dev locally and open http://localhost:3000/, and it shows me the login error again:

• 2.3 Then I tried to just type http://localhost:3000/, it shows me below:

and the two errors are:

and

• 2.4 Then I just said hello in the chat, and it gave me:

• 2.5 Finally, I tried to select a small region, and it gave me:

I hope I made my problem clear.

Best regards and many thanks,

[ShahabEJ]

@Amazingren, ok now you have the tables, which is good!

It seems the trigger that should populate the user_roles table doesn't work for some reason!

What you should then do is to populate the user_roles manually. For this, please follow the following link:

#6 (comment)

First, populate the user_roles table as mentioned in the above post. Then, check out the user_usage table, to see if it now contains a new row. If not, you need to populate that table as well.

Let me know if this fixes the issue.

[Amazingren]

Dear @ShahabEJ ,

It works for me now! (After manually creating the user_roles.)

Though I can randomly choose some areas, however, it seems I can not get the same visualization ability as what you did in the demo video (like the colorful map or the analysis chart).

Is this related to the region I choose or how should I also achieve that ability?

Best and manyt thanks,

[Navid61]

I removed the node_modules folder and package-lock.json from my previous configuration. Then, I reinstalled the Node packages and ran schema.sql. However, after installing the dependencies, when I ran npm run dev, I encountered the following error:

Module not found: Can't resolve 'lodash.isequal'
   7 | import useLayerSelectionStore from "@/features/maps/stores/use-layer-selection-store";
   8 | import useMapLayersStore from "@/features/maps/stores/use-map-layer-store";
>  9 | import isEqual from "lodash.isequal";
     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  10 | import useFunctionStore from "@/features/maps/stores/use-function-store";
  11 | import useMapDisplayStore from "@/features/maps/stores/use-map-display-store";

Is this issue related to my configuration, or should I investigate other possible causes? Any guidance on resolving this would be appreciated.

[ShahabEJ]

@Amazingren, my apologies for the delay!

it seems like it's not yet configured properly. I believe your GCP environment hasn't been configured correctly. Double check your GEE configs to see if your account service has has all the required permissions.

We'll release an update soon with much better error handling and messaging. Just busy with many thing right now 😄

---

@Navid61, my apologies for the delay!

You can install the lodash.isequal separately:
npm i lodash.isequal

I suspect, though, that even after doing that, you make get errors for some other packages, because it seems like there is a conflict between the .lock and the packages. Not sure, though. Give it a try and let me know if you still are facing this issue.

[Navid61]

@ShahabEJ Thank you for your response. That problem has been solved. Thank you. However, I have new issues that I will paste here:

Error: Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render.
    at createUnhandledError (http://localhost:3000/_next/static/chunks/node_modules_next_dist_client_523921._.js:689:49)
    at handleClientError (http://localhost:3000/_next/static/chunks/node_modules_next_dist_client_523921._.js:856:56)
    at error (http://localhost:3000/_next/static/chunks/node_modules_next_dist_client_523921._.js:991:56)
    at console.error (http://localhost:3000/_next/static/chunks/node_modules_@mantine_core_esm_b4f8df._.js:10208:13)
    at getRootForUpdatedFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:2456:143)
    at enqueueConcurrentHookUpdate (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:2439:16)
    at dispatchSetStateInternal (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:3944:22)
    at dispatchSetState (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:3917:9)
    at setRef (http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:17:16)
    at http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:26:29
    at Array.map (<anonymous>)
    at http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:25:31
    at setRef (http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:17:16)
    at http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:26:29
    at Array.map (<anonymous>)
    at http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:25:31
    at setRef (http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:17:16)
    at http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:26:29
    at Array.map (<anonymous>)
    at http://localhost:3000/_next/static/chunks/node_modules_@radix-ui_80d629._.js:25:31
    at runWithFiberInDEV (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:631:20)
    at safelyDetachRef (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:5937:37)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6495:82)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6617:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6617:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)
    at commitMutationEffectsOnFiber (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6413:17)
    at recursivelyTraverseMutationEffects (http://localhost:3000/_next/static/chunks/node_modules_next_dist_compiled_react-dom_1f56dc._.js:6404:106)

[Amazingren]

@Amazingren, my apologies for the delay!

it seems like it's not yet configured properly. I believe your GCP environment hasn't been configured correctly. Double check your GEE configs to see if your account service has has all the required permissions.

We'll release an update soon with much better error handling and messaging. Just busy with many thing right now 😄

@Navid61, my apologies for the delay!

You can install the lodash.isequal separately: npm i lodash.isequal

I suspect, though, that even after doing that, you make get errors for some other packages, because it seems like there is a conflict between the .lock and the packages. Not sure, though. Give it a try and let me know if you still are facing this issue.

Hi @ShahabEJ, Great! Thanks for everything, now all the things work for me. It was some env. setting problem from my side for the last problem.

Best regards and thanks very much for everything you provided,