FlutterFlow / flutterflow-issues

A community issue tracker for FlutterFlow.
118 stars 19 forks source link

getting Uncaught (in promise) during test / run/ published mode - (not because of my project issue, seems like flutterflow's appstate json issue) #3039

Closed ishanSiterecon closed 2 months ago

ishanSiterecon commented 3 months ago

Has your issue been reported?

Current Behavior

When I currently open the test mode (which was working perfectly 2 days ago with the same configs) - yesterday it was not working. Now that it is resolved somehow, the test build just not renders. It gives me error:

Uncaught (in promise) Error
    at Object.throw_ [as throw] (dart_sdk.js:11914:11)
    at Object._parseJson (dart_sdk.js:59836:19)
    at JsonDecoder.convert (dart_sdk.js:57585:22)
    at JsonCodec.decode (dart_sdk.js:57280:48)
    at Object.jsonDecode (dart_sdk.js:59826:25)
    at new app_state.FFAppState._internal (app_state.dart:569:45)
    at get _instance (app_state.dart:11:44)
    at desc.get [as _instance] (dart_sdk.js:12520:17)
    at FFAppState.new (app_state.dart:14:12)
    at main$ (main.dart:20:20)
    at main$.next (<anonymous>)
    at dart_sdk.js:49722:33
    at _RootZone.runUnary (dart_sdk.js:49577:59)
    at _FutureListener.thenAwait.handleValue (dart_sdk.js:44704:29)
    at handleValueCallback (dart_sdk.js:45304:49)
    at _Future._propagateToListeners (dart_sdk.js:45342:17)
    at [_completeWithValue] (dart_sdk.js:45183:23)
    at async._AsyncCallbackEntry.new.callback (dart_sdk.js:45217:35)
    at Object._microtaskLoop (dart_sdk.js:50026:13)
    at _startMicrotaskLoop (dart_sdk.js:50032:13)
    at dart_sdk.js:45573:9
throw_ @ dart_sdk.js:11914
_parseJson @ dart_sdk.js:59836
convert @ dart_sdk.js:57585
decode @ dart_sdk.js:57280
jsonDecode @ dart_sdk.js:59826
app_state.FFAppState._internal @ app_state.dart:569
get _instance @ app_state.dart:11
desc.get @ dart_sdk.js:12520
new @ app_state.dart:14
main$ @ main.dart:20
(anonymous) @ dart_sdk.js:49722
runUnary @ dart_sdk.js:49577
handleValue @ dart_sdk.js:44704
handleValueCallback @ dart_sdk.js:45304
_propagateToListeners @ dart_sdk.js:45342
[_completeWithValue] @ dart_sdk.js:45183
(anonymous) @ dart_sdk.js:45217
_microtaskLoop @ dart_sdk.js:50026
_startMicrotaskLoop @ dart_sdk.js:50032
(anonymous) @ dart_sdk.js:45573
Promise.then (async)
_scheduleImmediateWithPromise @ dart_sdk.js:45571
_scheduleImmediate @ dart_sdk.js:45577
_scheduleAsyncCallback @ dart_sdk.js:50047
_rootScheduleMicrotask @ dart_sdk.js:50229
scheduleMicrotask @ dart_sdk.js:49597
[_asyncCompleteWithValue] @ dart_sdk.js:45216
[_asyncComplete] @ dart_sdk.js:45198
complete @ dart_sdk.js:44580
(anonymous) @ storage_backend_js.dart:136
_checkAndCall @ dart_sdk.js:12169
dcall @ dart_sdk.js:12174
(anonymous) @ dart_sdk.js:119705

this seems some JSON issue with the app state but my app states were working completely earlier. and not forgot to mention that the app is not even initialized I believe? this clearly seems flutterflow's end issue. please look into it!

Screenshot 2024-06-01 at 9 39 36 PM

Expected Behavior

On using test mode, I should have been able to use my project's build to test and then start working on new requirements.

Steps to Reproduce

  1. open my project https://app.flutterflow.io/project/estimation-app-634ajc?tab=appValues&appValuesTab=state
  2. Go to test mode
  3. open console log and see error before even the app correctly launched

Reproducible from Blank

Bug Report Code (Required)

NA

Context

My project id - estimation-app-634ajc

Visual documentation

Screenshot 2024-06-01 at 9 41 51 PM

Additional Info

NA

Environment

FlutterFlow v4.1.54+ released May 30, 2024
Flutter version is 3.19.1
Chrome Version 125.0.6422.113 
Mac OS Sonoma 14.5 M1 8gb

General

Relative to the time the changes were made, data was lost within

When following my steps to reproduce, data loss happens

ishanSiterecon commented 3 months ago

some thing is breaking internally for Flutterflow's test mode data loading phase. please check this, cannot work on my project

Screenshot 2024-06-01 at 9 56 28 PM
leighajarett commented 3 months ago

Looking into it!

github-actions[bot] commented 3 months ago

This issue is stale because it has been open for 7 days with no activity. If there are no further updates, a team member will close the issue.

paulperez-dev commented 3 months ago

Hi @ishanSiterecon! We are unable to reproduce this issue. Can you please confirm us if it persists in the latest version?

paulperez-dev commented 2 months ago

Closing this issue since we haven't heard back from you. If you are still facing the problem please submit a new issue. Have a great day!