BUG: New server, new user, healthpod is failing
Open
@atangster is already working on this.
Since Aug 10, 2025.
- Dominant language
- Dart
- Stars
- 10
- Forks
- 7
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Using a new server with the latest CSS v7.1.7: https://pods.test.solidcommunity.au
I created a new user, then FILES -> BLOOD PRESSURE -> IMPORT to import the sample csv.
This imported just fine and I could see the VIEW
Exit from the app took a very long time.
Restart the app and go to VIEW:
Yet within FILES I see
Console reported:
❌ Retry failed, file still encrypted
❌ Retry failed, file still encrypted
[ERROR:flutter/runtime/dart_vm_initializer.cc(40)] Unhandled Exception: setState() called after dispose(): _BPEditorPageState#9741e(lifecycle state: defunct, not mounted)
This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback.
The preferred solution is to cancel the timer or stop listening to the animation in the dispose() callback. Another solution is to check the "mounted" property of this object before calling setState() to ensure the object is still in the tree.
This error might indicate a memory leak if setState() is being called because another object is retaining a reference to this State object after it has been removed from the tree. To avoid memory leaks, consider breaking the reference to this object during dispose().
#0 State.setState.<anonymous closure> (package:flutter/src/widgets/framework.dart:1163:9)
#1 State.setState (package:flutter/src/widgets/framework.dart:1198:6)
#2 _BPEditorPageState._loadData (package:healthpod/features/table/bp_editor/page.dart:86:7)
<asynchronous suspension>
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.