Repository navigation
Fix signed-in actions in production, trim unused push services, fix screenshot workflow - #17
Merged
Merged
Conversation
Appwrite Cloud's edge executor overwrites the Authorization header before a request reaches refetch.io, so every /api/app/* call answered 401 in production (the JWT itself checked out: 200 from Appwrite's /v1/account). Pairs with refetch-io/refetch#14. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
appwrite 28 brings an MQTT foreground service (remoteMessaging), flutter_background_service and boot receivers. Refetch pushes through FCM with the push plugin and never starts them; left in, the remoteMessaging foreground service needs a Play Console declaration and the receivers wake the app on every reboot. Removed with tools:node=remove, as the appwrite manifest suggests. The merged manifest keeps the push plugin's FCM receiver and MESSAGING_EVENT service. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
android-emulator-runner runs each script line as its own command, so the backslash-continued flutter drive fell apart (Target file "\\" not found). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three fixes found while taking #16 live.
X-Refetch-JWT. Signed-in actions (vote, comment, submit, profile sync) all answered 401 in production. Appwrite Cloud's edge executor overwritesAuthorizationwith its ownBasic opr:<secret>before the request reaches refetch.io. On the phone, the same JWT returned 200 from Appwrite's/v1/accountand 401 from/api/app/session. Needs Read the app JWT from X-Refetch-JWT; Cloud's executor overwrites Authorization refetch#14 deployed first.remoteMessagingforeground service,flutter_background_service, the boot receivers, and theFOREGROUND_SERVICE*/RECEIVE_BOOT_COMPLETEDpermissions. Refetch pushes through FCM with thepushplugin. Left in, the foreground service needs a Play Console declaration, and the receivers wake the app on every reboot. The merged manifest still has the push plugin's FCM receiver andMESSAGING_EVENTservice.android-emulator-runnerruns eachscript:line as its own command, so the multi-lineflutter drivebroke. It's now one line.flutter analyzeis clean, andflutter testpasses 65 (new: the JWT travels inX-Refetch-JWT, notAuthorization). The debug APK builds, and I checked the merged manifest.Local push errors (
Default FirebaseApp is not initialized) are expected:google-services.jsonis gitignored and only injected by the release workflow.🤖 Generated with Claude Code