After upgrading Jaspr to v0.12.0, I discovered an issue where pages would not render with infinity browser loading when using SyncProvider. I confirmed that if I remove SyncProviderDependencies and preloadDependencies from the component, rendering itself is possible, but there are cases where data from SyncProvider is not rendered properly because preload does not proceed.
Note: In this official example, the app appears to run properly even though I remove SyncProviderDependencies. However, when I actually used it in my projects, I found that in many cases, if SyncProviderDependencies was removed and preload did not proceed, the data was not rendered properly
Doctor Output
[✓] Jaspr CLI (Version 0.12.0)
• Dart Version 3.3.4 (stable) (Tue Apr 16 19:56:12 2024 +0000) on "macos_arm64" at /opt/homebrew/Caskroom/flutter/3.19.6/flutter/bin/cache/dart-sdk/bin/dart
• Running on macos Version 14.4.1 (Build 23E224) - Locale ko-KR
• Analytics: Enabled
[✓] Current Project
• Dependencies on core packages:
• jaspr: ^0.12.0
• jaspr_builder: ^0.12.0 (dev)
• jaspr_riverpod: ^0.3.11
• Rendering mode: server
• Uses jaspr compilers: false
• Uses flutter embedding: false
Expected Behavior
Pages should be rendered properly with synced data
Description
After upgrading Jaspr to v0.12.0, I discovered an issue where pages would not render with infinity browser loading when using
SyncProvider
. I confirmed that if I removeSyncProviderDependencies
andpreloadDependencies
from the component, rendering itself is possible, but there are cases where data fromSyncProvider
is not rendered properly because preload does not proceed.Steps To Reproduce
SyncProviderDependencies
. However, when I actually used it in my projects, I found that in many cases, ifSyncProviderDependencies
was removed and preload did not proceed, the data was not rendered properlyDoctor Output
Expected Behavior
Pages should be rendered properly with synced data