feat: Android SDK update for version 29.1.0-rc.3

[ArnabChatterjee20k]

This PR contains updates to the Android SDK for version 29.1.0-rc.3.

What's Changed

• Added: first background subscription auto-requests POST_NOTIFICATIONS (Android 13+) from the visible activity
• Fixed: onOpen/onClose callbacks fire correctly when joining or leaving the background host
• Fixed: notification taps are recorded after launching the app, so tap-opened screens land on top

Regenerated with sdk-generator 5.5.2.

[hansi-codes]

🔵 Tier A · Mergeable after minor fixes

The new permission prompting can duplicate explicit requests, and background connection callbacks still have a deduplication race.

Updates the Android SDK to 29.1.0-rc.3 and expands background push support with foreground-notification controls, permission helpers, refreshed authentication, revised scheduling, and bounded image decoding. Adds notification-tap APIs and an internal tap activity, forwards background connection lifecycle events, and automatically requests notification permission for background subscriptions.

Latest changes: The newest commit bumps the version to rc.3, adds automatic notification-permission prompting, tracks background connection state when joining or leaving the host, and records notification taps after requesting the app launch.

Verdict	New comments	Fixed	Still open
✅ Approved	2	0	1

	Finding	Where
🟡	Coordinate automatic prompts with explicit permission requests	library/src/main/java/io/appwrite/services/Push.kt:997
🟡	Make background connection deduplication atomic	library/src/main/java/io/appwrite/services/Push.kt:555

Fix with agent prompt

### Issue 1
library/src/main/java/io/appwrite/services/Push.kt:997-1000
**Coordinate automatic prompts with explicit permission requests**

`requestNotificationPermission()` never updates `asked`, so apps following the existing pattern of requesting permission and then subscribing immediately issue a second request while the first dialog is open; Android rejects overlapping requests and can deliver an empty permission result. If they subscribe after a denial instead, the SDK immediately prompts again—please share request state with the explicit helper.

### Issue 2
library/src/main/java/io/appwrite/services/Push.kt:555-559
**Make background connection deduplication atomic**

When joining a saved connection, `hostInBackground()` can call this on the caller thread while the MQTT connected listener calls it on its own thread. Both can read `backgroundOpen == false` before either writes it, firing `onOpen` twice despite the new deduplication; serialize the state transition and callback dispatch.

### Issue 3
CHANGELOG.md:5
**Describe the push behavior changes in the release notes**

This release changes SDK code substantially, including suppressing foreground notifications by default and adding `notifyInForeground` and background-permission APIs. Saying there are no SDK code changes hides a user-visible behavior change and the option consumers need to restore notifications.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

📂 Walkthrough · 9

File	Change
CHANGELOG.md	Adds release entries through rc.3 describing push APIs and lifecycle fixes.
README.md	Updates dependency versions and documents foreground notifications, background permissions, notification taps, and automatic permission prompting.
library/src/main/AndroidManifest.xml	Registers the internal notification-tap activity.
library/src/main/java/io/appwrite/Client.kt	Updates the SDK request-header version to 29.1.0-rc.3.
library/src/main/java/io/appwrite/services/Push.kt	Adds tap APIs, foreground controls, permission helpers and automatic prompting, cookie authentication fallback, and background lifecycle tracking.
library/src/main/java/io/appwrite/services/PushBackground.kt	Reworks authentication, scheduling, acknowledgement draining, image limits, notification filtering and tap intents, and tracks live connection state.
library/src/main/java/io/appwrite/services/PushCore.kt	Adds background-status metadata and refreshable MQTT authentication and reconnect handling.
library/src/main/java/io/appwrite/services/PushOpenActivity.kt	Launches the app with payload extras before recording and dispatching notification taps.
library/src/main/java/io/appwrite/services/PushWakeups.kt	Passes job identity and drain windows to background runs and delegates alarms to expedited jobs.

⏳ Still open from earlier reviews · 1

• 🟡 Describe the push behavior changes in the release notes · CHANGELOG.md:5

---

_{Reviewed the commits since 40fbc3a · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.}

[hansi-codes]

🟡 Tier B · 1 blocking finding to address. Summary

[hansi-codes]

Describe the push behavior changes in the release notes

This release changes SDK code substantially, including suppressing foreground notifications by default and adding notifyInForeground and background-permission APIs. Saying there are no SDK code changes hides a user-visible behavior change and the option consumers need to restore notifications.

Prompt To Fix With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 5

Comment:
**Describe the push behavior changes in the release notes**

This release changes SDK code substantially, including suppressing foreground notifications by default and adding `notifyInForeground` and background-permission APIs. Saying there are no SDK code changes hides a user-visible behavior change and the option consumers need to restore notifications.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟡 Minor · documentation · Reply if this doesn't apply.}

[hansi-codes]

🟡 Tier B · 1 blocking finding to address. Summary

[hansi-codes]

🔵 Tier A · Looks good to merge. Summary

[hansi-codes]

Coordinate automatic prompts with explicit permission requests

requestNotificationPermission() never updates asked, so apps following the existing pattern of requesting permission and then subscribing immediately issue a second request while the first dialog is open; Android rejects overlapping requests and can deliver an empty permission result. If they subscribe after a denial instead, the SDK immediately prompts again—please share request state with the explicit helper.

Prompt To Fix With AI

This is a comment left during a code review.
Path: library/src/main/java/io/appwrite/services/Push.kt
Line: 997-1000

Comment:
**Coordinate automatic prompts with explicit permission requests**

`requestNotificationPermission()` never updates `asked`, so apps following the existing pattern of requesting permission and then subscribing immediately issue a second request while the first dialog is open; Android rejects overlapping requests and can deliver an empty permission result. If they subscribe after a denial instead, the SDK immediately prompts again—please share request state with the explicit helper.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟡 Minor · bug · Reply if this doesn't apply.}

[hansi-codes]

Make background connection deduplication atomic

When joining a saved connection, hostInBackground() can call this on the caller thread while the MQTT connected listener calls it on its own thread. Both can read backgroundOpen == false before either writes it, firing onOpen twice despite the new deduplication; serialize the state transition and callback dispatch.

Prompt To Fix With AI

This is a comment left during a code review.
Path: library/src/main/java/io/appwrite/services/Push.kt
Line: 555-559

Comment:
**Make background connection deduplication atomic**

When joining a saved connection, `hostInBackground()` can call this on the caller thread while the MQTT connected listener calls it on its own thread. Both can read `backgroundOpen == false` before either writes it, firing `onOpen` twice despite the new deduplication; serialize the state transition and callback dispatch.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟡 Minor · concurrency · Reply if this doesn't apply.}