453 comments found.
The code fix for the firebase worked. However, it doesn’t save the display name in state now. Only the role and the email
const signUp = useCallback(({ email, password, displayName }: SignUpPayload) => { const signUpResponse = new Promise<firebase.auth.UserCredential>((resolve, reject) => { firebase .auth() .createUserWithEmailAndPassword(email, password) .then((userCredential) => { userCredential.user.updateProfile({ displayName }); updateUser( UserModel({ uid: userCredential.user.uid, data: { displayName, email: userCredential.user?.email, }, role: [‘admin’], }), ); resolve(userCredential); }) .catch((_error) => { const error = _error as firebase.auth.Error; reject(error); }); });
return signUpResponse;
}, []);
replace this method in FirebaseAuthProvider.tsx with this and it persists the data for the display name.
Thanks for the contribution.
In the mean time, please checkout our latest update:
its worth: https://react-material.fusetheme.com/documentation/changelog
Despite reaching out for support, we have not received any response for over three days. This lack of support is concerning.
We’re experiencing an issue with Firebase authentication where the login process never redirects. After signing up, the user is successfully created in the Firebase Authentication system, but the onAuthStateChanged listener is incorrectly looking for the user in the Realtime Database, where no data is present. This mismatch between authentication and database storage is causing significant problems in our application’s user flow.
Hi Aung,
I have resolved the issue with this commit;
https://github.com/withinpixels/fuse-react/commit/5ea90ebb4c9c163c0fca38049da8848a80b0b9afthanks for reporting the issue on support system.
I will release an update but you can also pull from the github repository.
Kind regards.
is it available pure react version with out vite ? i mean with react-creat-app
Hi, we were using create-react-app, you can find earlier versions at github repository,
There are lots of reasons to migrate:
- create-react-app no longer actively developing - Really Faster Build Times: Vite uses ES modules, resulting in quicker builds and hot module replacement. - Optimized Production Builds: Rollup-based production builds are more efficient and smaller. - Better TypeScript Support: Easier configuration for TypeScript projects. - Improved HMR: Faster and more reliable hot module replacement. - SSR and SSG Support: Built-in support for server-side rendering and static site generation.
Kind regards,
Does anyone else have the experience of setting up all the firebase fields in the .env file and then when you sign in or log in it just hangs in the loading screen state? No errors or anything. Not to mention all 2xx codes. Kinda hard to debug when there’s not errors. haha.
Could you open support ticket at support.withinpixels.com
The issue probably related with user role and route.auth configuration.
Unfortunately my support has expired and I’m not in a position to renew it at the moment. I have the base skeleton template and I changed the .env to have the correct firebase values. That’s all I’ve done. I can confirm it’s hitting firebase and creating the user.
For anyone else having this issue, I believe the issue is when creating a new user with firebase it doesn’t add to any firestore or anything of that nature so it doesn’t every return a user that conforms to the Fuse User interface. I’m going to test this and report back. 
nope. No luck
Ok. Can you at least answer this? If I’m using the base skeleton is Should I have to do anything other than fill in the .env file to make firebase work?
Hi, please report issues with support platform: support.withinpixels.com
The related issue is resolved with the commit:
https://github.com/withinpixels/fuse-react/commit/5ea90ebb4c9c163c0fca38049da8848a80b0b9afKind regards.
Thank you for that. Looks like the displayName field still isn’t persisting.
I really like your template, but I have a question before buying.
I noticed that in the side menu the submenus remain open when you switch from one menu to another, even though none of their children are active.
Is it possible to configure it so that it only keeps a menu open if any of its children are active?
Hi, it’s intended behavior but yes its possible to configure as you describe.
Can someone help me with firebase auth? i have set up all the corect details but auth is not working.
Hi, please open support request at support.withinpixels.com
Are there any plans to support Remix, especially in light of their announcement that the will be rolling Remix into Router v7?
Hi, We haven’t think about it yet, if remix has more common usage in community, we might consider.
Thanks for the information.
Hi, I can see that you are using Mock API for JWT integration. I want to use my custom API for JWT user authentication. Do you have any documentation for it? Or can you please guide me to integrate my custom API for user authentication.
Hi,
Checkout api endpoints at src/app/auth/services/jwt/jwtAuthConfig.ts You need to change them with yours.
And checkout, reuqest responses at https://react-material.fusetheme.com/documentation/mock-api to adapt with your api.
Kin regards.
I’ve already joined https://github.com/withinpixels/fuse-react, which is based on TypeScript. Is there a GitHub repository specifically for JavaScript?
You can checkout js-demo and js-skeleton branches for js versions.
Is there really not going to be a NextJS version of Fuse?
Hello, it is not planned in the near future.
Dear support, may I know how much is the ongoing support if I need support after first year?
You can renew support on themeforest.
Yes I know I can renew support, but we’d love to know how much is it as we have to apply for budgeting for my company.
Currently 21.88$
It says 6 month costs 62.5% of item price. So 1 year should be 105% of item price? So it should be 873 USD per year? Am I correct?
Yes, i said for Regular license, these ratios are also valid for extended license type.
I lot of developer are asking Next.js version. Of course it is different but we really need such kind of theme in Next.js. Waiting for it.
Hello, it is not planned in the near future.
Hello, I sent a custom license request to you last week but seems no one respond. Can help to reply us please?
Where can find documentation ?
I need a quotation for this product to give to my company to continue the purchase process. I’d like extend license and extend support, what can I do?
please checkout: https://fusetheme.com/pricing/
I need a quote to give to my company I’d like extend license and extend support, what can I do?
please checkout: https://fusetheme.com/pricing/
Besides the major limitation of production only builds as described in the previous post, what is the advantage of react-app-rewired? It seems so out of date. Other than it’s a builder (which there are many others, perhaps better), it seems to be used for path aliases like @fuse and @history. This feature has been a native capability in NodeJS.
Check out: https://nodejs.org/api/packages.html#self-referencing-a-package-using-its-name
Could you open ticket at support.withinpixels.com
Could you checkout changelog and latest releases. We are currently using Vite.js ESM not webpack anymore
Need help with react-app-rewired. We deploy to different environments (dev, prod, etc.). react-app-rewired always uses production no matter what the NODE_ENV is to by environment variable, cross-env, or some alternative. Consequently, I can’t point to a dev or test environment.
Suggestions?
It has to do with react-app-rewired build script forcing NODE_ENV to production. I raised an issue here: https://github.com/timarney/react-app-rewired/issues/655 But the code has forced production for the last 8 years. Unless I’m wrong, react-app-rewired only allows building in production mode, making this solution incompatible with modern cloud hosting environments that need more than a production environment.
This is a serious show stopper for us that wasn’t apparent until recently. As you know having recently adopted Firebase Auth, GCP (and I most deployment techniques, Azure as well) requires building (‘rewired bundling’ in this case) prior to deployment. So, after months of development, we need to change course unless you know something I don’t. Please advise.
Turns out, it’s possible, at least for my current build process. In my case, we’re deploying to multiple Google Projects, each with their own configuration. So, I can’t have a .env.production file for it get’s automatically picked up by react_scripts build process even regardless of settings or environment variables. So, thanks to the Firebase Team thinking through an amazing hosting/development model, it works using the code below. Where this model breaks down quickly is when I need to, for example, configure connecting to more than one database, or things that aren’t loaded by default for me in the environment. In that case, as with many other multi-env build scenarios I’ve seen, this are still challenges with rewired and react-scripts.
Note: I’m using Fuse version 8.3.8. Maybe the latest version has a better option. But I’m doubtful given it’s still dependent on rewired and react-scripts.
if(process.env.NODE_ENV == null){
app = initializeApp(); // google will values that match host environment
}
else {
app = initializeApp({
apiKey: process.env.REACT_APP_FIREBASE_API_KEY,
...
})
}
Could you open ticket at support.withinpixels.com
We are currently using ViteJS, could you checkout latest releases.
I was looking for the right place for bug reports but didn’t find any, so leaving it here: If on Scrum boards, inside one of the boards you click on settings, close settings, then open one of the cards and close it, the whole page will slide left and be in a stuck mode. If you release any fix please comment back to this comment. Thx a lot, and kudos for this awesome template.
General help for others getting firebase auth to work. I copied values from the firebase console into the env file. It took me a while to realize I needed to remove the commas added by Firebase in “Project Settings” / “SDK setup and configuration”. This should have been obvious but caused me to loose an hour on troubleshooting. Hopefully this saves someone time.
Thanks for your contribution!c 