Skip to content

Dev -> Staging [5.1.0]#162

Merged
navratan-soni merged 21 commits into
stagingfrom
dev-5.1.0
Jun 5, 2026
Merged

Dev -> Staging [5.1.0]#162
navratan-soni merged 21 commits into
stagingfrom
dev-5.1.0

Conversation

@Harjot1508

Copy link
Copy Markdown
Contributor

No description provided.

spoorthipujariadobe and others added 21 commits October 20, 2025 09:45
Staging -> Main for Messaging and Core 5.0.1
Expose setPushIdentifier on Android and iOS so Flutter apps can
register a push notification token directly through the Dart API
without dropping down to native code.

- Dart: MobileCore.setPushIdentifier(String? token)
- Android: handleSetPushIdentifier follows handleSetAdvertisingIdentifier pattern
- iOS: converts NSString token to NSData via NSUTF8StringEncoding before
  calling [AEPMobileCore setPushIdentifier:]
- Tests: added group covering token and null cases
- Docs: CHANGELOG 5.0.2 entry and README API section
Add a second method that accepts Uint8List? and passes the bytes
directly to [AEPMobileCore setPushIdentifier:] as NSData on iOS,
without any UTF-8 or hex encoding — which is the correct behaviour
for raw APNs device tokens.

On Android the method is a no-op with a debug log; developers should
use setPushIdentifier(String?) with the FCM token there.

- Dart: import dart:typed_data, add setPushIdentifierWithData(Uint8List?)
- iOS: handleSetPushIdentifierWithData uses FlutterStandardTypedData.data
- Android: no-op handler with debug log
- Tests: 25/25 passing
…ersion

- Remove setPushIdentifierWithData; a single setPushIdentifier(String?) now
  handles both Android (FCM token) and iOS (APNs hex token)
- Fix iOS bridge: convert hex string to NSData internally instead of
  UTF-8 encoding, which was registering wrong bytes with the AEP SDK
- Fix corrupted .gitignore line that merged two entries into one
- Update CHANGELOG, README and tests accordingly
feat(core): add MobileCore.setPushIdentifier API
[MOB-24978] refresh InApp bug fix
@navratan-soni navratan-soni merged commit 657b8a9 into staging Jun 5, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants