You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally, the page does open, but I see the following message in the console As long as the current environment was not considered as the Telegram-based one, it was mocked. Take a note, that you should not do it in production and current behavior is only specific to the development process. Environment mocking is also applied only in development mode. So, after building the application, you will not see this behavior and related warning, leading to crashing the application outside Telegram.
What could be causing this issue?
I also have a few other questions:
Is it possible to use state managers (MobX/Redux)?
Can we use Tailwind CSS or UI libraries?
Everything seems to be working, but could there be any problems or conflicts in production?
demo1.mp4
The text was updated successfully, but these errors were encountered:
vovajr11
changed the title
Redirected back(homa page) after open http://localhost:5173/reactjs-template
Redirected back(home page) after open http://localhost:5173/reactjs-template
Aug 24, 2024
Hello friends!
I'm new to TMA and need some help.
When I try to open the link http://localhost:5173/reactjs-template, I can’t view the page in the browser, it keeps redirecting me back.
Occasionally, the page does open, but I see the following message in the console
As long as the current environment was not considered as the Telegram-based one, it was mocked. Take a note, that you should not do it in production and current behavior is only specific to the development process. Environment mocking is also applied only in development mode. So, after building the application, you will not see this behavior and related warning, leading to crashing the application outside Telegram.
What could be causing this issue?
I also have a few other questions:
Everything seems to be working, but could there be any problems or conflicts in production?
demo1.mp4
The text was updated successfully, but these errors were encountered: