For Flutter developers whose home screen widget stays blank
Widget BridgeAn App Group that differs by one word, a key spelt two ways, an int read as a String. Line up the Flutter, iOS and Android sides, then get the corrected files.
Paste the widget's files - the Flutter side, the SwiftUI extension, the Android provider, its layout and manifest. Your browser lines up every key written and read with its type, matches the App Group, the iOS widget kind and the Android provider against what updateWidget asks for, and flags UserDefaults.standard, a provider that never calls updateAppWidget, view ids the layout lacks and saves not awaited. Then the review, and the corrected files.
The widget files free
The scan free
What the scan found
The key map
The skill's widget workflows
The setup steps, and the checklist free
What no file shows: the Widget Extension target, the App Groups capability on both targets, the manifest receiver and its widget info - the skill's native steps, filled in with this widget's names.
setup.md
The review metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved reviews
How it works - and what it cannot see
The scan splits the paste at its file lines and reads each file with comments and strings masked, resolving the string constants each one defines - so it can tell that appGroupId in Dart is group.com.example.news while Swift asks for group.com.example.app. It follows the skill's data flow: the Flutter app sets the App Group, saves key-value pairs with home_widget and calls updateWidget; the SwiftUI TimelineProvider reads them from UserDefaults(suiteName:); the Android AppWidgetProvider reads them through HomeWidgetPlugin.getData and pushes RemoteViews with updateAppWidget.
It cannot see a key built at run time, the Xcode capabilities or the provisioning, or what the widget shows when its data is stale - that is the review, and the setup steps. The page re-scans the rewritten files, so a fix that did not land is flagged rather than trusted, and every file and class keeps its name.