Can we access your project?
Current Behavior
Permission to access project: cors-issue-demo-b2a7a0
When using the test mode feature, the test mode fails due to a 401 Unauthorized strict-origin-when-cross-origin error.
Request URL:
https://tm-prod.dreamflow.cloud/72f860f9-525d-4b3e-b4fd-d23c484d17d7/preview/cors-issue-demo-b2a7a0/
Method: GET
Expected Behavior
I expect the test mode to run without access issues. Also, the stability of the test mode needs attention given this issue is resolved. Extra info at the bottom.
Steps to Reproduce
- Create a new project
- Press Test Mode
Reproducible from Blank
Bug Report Code (Required)
IT48lcmBw4VgoeFK187ude9VnjwXJjI7UL83isEbZA88J5zKB+wAYvf7P1FWTLynS3NcMU2j/To1/PfqveHTEMdeOQ6Wf4RRzaV+WhbwQnGtVYiJOrm/fW1RGfFPIBzH4bWG3Qp4FOlecU5k3V6IBN6RbC3qNZf4OmwnHfG1KdeK2SrDX1iXc2URm05KZDPz
Visual documentation
Environment
- FlutterFlow version: 6.6.111
- Platform: Windows
- Browser name and version: Chrome 148.0.7778.179 (Official Build) (64-bit)
- Operating system and version affected: Win10
Additional Information
Run mode is working fine though I do prefer the test mode given the regular FlutterFlow windows app crashes I experience with run mode. Most of my time lost whilst working with FlutterFlow before this issue was from inconsistent Test Mode stability, often failing and requiring multiple hot reloads in the browser to get the application to run. It can take up to 15mins for me to get into the app on bad days. At the moment, being forced to use the more unstable Run mode is costing me up to a couple of hours work per day, inline with the time lost on Test mode given that I was not experiencing this issue.
Can we access your project?
Current Behavior
Permission to access project: cors-issue-demo-b2a7a0
When using the test mode feature, the test mode fails due to a 401 Unauthorized strict-origin-when-cross-origin error.
Request URL:
https://tm-prod.dreamflow.cloud/72f860f9-525d-4b3e-b4fd-d23c484d17d7/preview/cors-issue-demo-b2a7a0/
Method: GET
Expected Behavior
I expect the test mode to run without access issues. Also, the stability of the test mode needs attention given this issue is resolved. Extra info at the bottom.
Steps to Reproduce
Reproducible from Blank
Bug Report Code (Required)
IT48lcmBw4VgoeFK187ude9VnjwXJjI7UL83isEbZA88J5zKB+wAYvf7P1FWTLynS3NcMU2j/To1/PfqveHTEMdeOQ6Wf4RRzaV+WhbwQnGtVYiJOrm/fW1RGfFPIBzH4bWG3Qp4FOlecU5k3V6IBN6RbC3qNZf4OmwnHfG1KdeK2SrDX1iXc2URm05KZDPz
Visual documentation
Environment
Additional Information
Run mode is working fine though I do prefer the test mode given the regular FlutterFlow windows app crashes I experience with run mode. Most of my time lost whilst working with FlutterFlow before this issue was from inconsistent Test Mode stability, often failing and requiring multiple hot reloads in the browser to get the application to run. It can take up to 15mins for me to get into the app on bad days. At the moment, being forced to use the more unstable Run mode is costing me up to a couple of hours work per day, inline with the time lost on Test mode given that I was not experiencing this issue.