kapa.ai
WWasp-lang
•Created by DavidFeng on 10/17/2024 in #🙋questions
Google Auth Redirection Not Working (Netlify & AWS)
Sorry @DavidFeng, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
5 replies
WWasp-lang
•Created by DavidFeng on 10/17/2024 in #🙋questions
Google Auth Redirection Not Working (Netlify & AWS)
----------------------
Hmm, I don't know enough to give you a confident answer yet. However, based on the knowledge sources provided, it seems like you might need to check your Google OAuth app settings and ensure that the correct redirect URIs are set.
In the Google Cloud Platform console, under the OAuth consent screen, you should have your redirect URIs set to
<http://localhost:3001/auth/google/callback> for local development and <https://your-server-url.com/auth/google/callback> for your deployed server. Replace your-server-url.com with the actual URL of your deployed server.
Also, ensure that your Google client ID and secret are correctly set in your .env.server file.
Here are the relevant documentation links for setting up Google Auth in Wasp:
- Creating a Google OAuth App (https://wasp-lang.dev/docs/auth/social-auth/google#3-creating-a-google-oauth-app)
- Adding Environment Variables (https://wasp-lang.dev/docs/auth/social-auth/google#4-adding-environment-variables)
If you're still having trouble, it might be helpful to check your main.wasp file and ensure that your Google userSignupFields and configFn match the latest implementation as shown in the OpenSaas repository (https://github.com/wasp-lang/open-saas/blob/main/app/src/server/auth/setUsername.ts#L29-L39).
Please note that these instructions are specific to Wasp and may not directly apply to your deployment on Netlify and AWS EC2.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------5 replies
WWasp-lang
•Created by DavidFeng on 10/17/2024 in #🙋questions
Google Auth Redirection Not Working (Netlify & AWS)
Hi @DavidFeng. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
5 replies
WWasp-lang
•Created by victor on 10/17/2024 in #🙋questions
deploy in fly.io with multiple environment
Sorry @victor, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
4 replies
WWasp-lang
•Created by victor on 10/17/2024 in #🙋questions
deploy in fly.io with multiple environment
----------------------
To deploy your Wasp app on Fly.io, you can use the Wasp CLI's
setup command. This command creates your client and server apps on Fly.io and adds some secrets, but it does not deploy them. The command is as follows:
The <app-name> is the name of your app and <region> is the region where your app will be deployed. You can find the available regions here (https://wasp-lang.dev/docs/advanced/deployment/cli#flyio-regions).
After running setup, Wasp creates two new files in your project root directory: fly-server.toml and fly-client.toml. You should include these files in your version control. You can edit these files to further configure your Fly deployments.
If you want to maintain multiple apps (for example, for different environments like production, staging, and development), you can add the --fly-toml-dir <abs-path> option to point to different directories.
Remember to only run setup once per app. If you run it multiple times, it will create unnecessary apps on Fly.
For deploying the app, you can use the launch command which runs setup, create-db, and deploy in sequence.
If your app requires any other environment variables, you can set them with the --server-secret option:
Please refer to the Wasp CLI documentation (https://wasp-lang.dev/docs/advanced/deployment/cli#setup) for more details.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------4 replies
WWasp-lang
•Created by victor on 10/17/2024 in #🙋questions
deploy in fly.io with multiple environment
Hi @victor. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
4 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
Sorry @wardbox, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
----------------------
I'm sorry, but I can't provide a helpful answer without the error log. Could you please provide the full error log? This will help me understand the issue better and provide a more accurate solution.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
Let me check the knowledge base for you again. One moment! :books:
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
Sorry @wardbox, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
----------------------
The version of Prisma you're using might be causing the issue. Wasp has specific compatibility with certain versions of Prisma. For instance, it was noted in one of the issues that Prisma introduced breaking changes in version 2.13, and Wasp had to fix the version to 2.12 to avoid problems (source (https://github.com/wasp-lang/wasp/issues/158)).
Also, Wasp had issues with Node version 16.15.1 due to npm not seeing locally installed packages, which caused Wasp to use the wrong Prisma version (source (https://github.com/wasp-lang/wasp/issues/631)).
Please ensure you're using a compatible version of Node.js and Prisma with Wasp. If the problem persists, consider opening an issue in the Wasp Github repository (https://github.com/wasp-lang/wasp/issues) for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
Let me check the knowledge base for you again. One moment! :books:
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
Sorry @wardbox, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
----------------------
The error messages you're seeing indicate that the Prisma client is not recognizing your entities. This could be due to a few reasons:
1. Prisma client not being generated correctly: If the Prisma client is not generated correctly, it won't recognize your entities. You can try regenerating the Prisma client by running
wasp db migrate-dev. This command will apply the latest changes to your database and also regenerate the Prisma client (source (https://github.com/wasp-lang/wasp/issues/214)).
2. Incompatible Prisma version: If you're using an incompatible version of Prisma, it could lead to issues like this. Wasp has fixed the version of Prisma to avoid such problems. Make sure you're using the correct version of Prisma (source (https://github.com/wasp-lang/wasp/issues/158)).
3. Issues with the Wasp compiler: If there are issues with the Wasp compiler, it might not be able to compile the SDK correctly, leading to these errors. You can try running wasp clean followed by wasp start to clean the build artifacts and start the Wasp compiler again (source (https://discord.com/channels/686873244791210014/1215750573278629958)).
If none of these solutions work, it might be helpful to check if there's a package.json file in a directory above your Wasp project that specifies a different Prisma version. This could cause npm to use the wrong Prisma version (source (https://github.com/wasp-lang/wasp/issues/787)).
If you're still facing issues, please provide more details or consider opening an issue in the Wasp Github repository (https://github.com/wasp-lang/wasp/issues).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------18 replies
WWasp-lang
•Created by wardbox on 10/17/2024 in #🙋questions
Migrating from v0.14 to v0.15, entities not found
Hi @wardbox. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
18 replies
NNormal
•Created by Robi🐋 on 10/5/2024 in #🤝ask-a-question
Normcore Meta Avatars Setup Issues
26 replies
NNormal
•Created by Robi🐋 on 10/5/2024 in #🤝ask-a-question
Normcore Meta Avatars Setup Issues
----------------------
The error message you're seeing typically occurs when Unity is unable to find a
.meta file for an asset. .meta files are used by Unity to store import settings and other information about assets.
In your case, the asset in question is Normal.Realtime.sln, which is part of the Normcore package. This file is located in an immutable folder, meaning it's part of a package and should not be modified.
Here are a few steps you can take to resolve this issue:
1. Reimport the Normcore package: This can be done by going to the Unity Package Manager, finding the Normcore package, and clicking the "Reimport" button. This should force Unity to regenerate the .meta file for the Normal.Realtime.sln asset.
2. Delete and reinstall the Normcore package: If reimporting doesn't work, you can try deleting the Normcore package and then reinstalling it. This can be done from the Unity Package Manager. Be sure to back up any important data before doing this, as deleting the package will remove all of its contents.
3. Check your Unity version: Ensure that you're using a version of Unity that is compatible with the version of the Normcore package you're using. You can check the Normcore documentation (https://normcore.io/documentation/essentials/getting-started) for information on which versions of Unity are supported.
If none of these steps resolve your issue, I recommend reaching out to the Normcore community on their Discord (https://normcore.io/documentation/essentials/common-questions#does-normcore-support-x-y-z) for further assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------26 replies
NNormal
•Created by Robi🐋 on 10/5/2024 in #🤝ask-a-question
Normcore Meta Avatars Setup Issues
Let me check the knowledge base for you again. One moment! :books:
26 replies
WWasp-lang
•Created by Adam on 10/17/2024 in #🙋questions
Regarding ask-the-documents WSL2 solution to compile
Sorry @Adam, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
7 replies
WWasp-lang
•Created by Adam on 10/17/2024 in #🙋questions
Regarding ask-the-documents WSL2 solution to compile
Also, please be aware that the
vector extension is not officially supported by Prisma, the database toolkit used by Wasp. As a result, you may need to use raw SQL queries to interact with vector data types in your database (source (https://github.com/wasp-lang/wasp/issues/1215)).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------7 replies