Can i use Klaviyo.INSTANCE.setPushToken(token) in another process

[qiaop]

Checklist

• I have read the contributing guidelines
• I have determined whether this bug is also reproducible in a vanilla Android project
• If possible, I've reproduced the issue using the master branch or latest release of this package.
• This issue hasn't been addressed in an existing GitHub issue or pull request.

Description

My FirebaseMessagingService is in another porocess,an Klaviyo ini in main process.
how can i use Klaviyo.INSTANCE.setPushToken(token) in FirebaseMessagingService onNewToken

Expected behavior

always

Actual behavior

always

Steps to reproduce

always

The Klaviyo Android SDK version information

3.0.0

Device Information

No response

Android Studio Version

No response

Android API Level

No response

[dan-peluso]

Thanks for filing this! While it's definitely recommended that you use the application to encapsulate both your Klaviyo instance and Firebase service, there are some workarounds for messaging between the two. I'd recommend looking into using shared preferences to hold the firebase token, or creating a broadcast between the services that handles the token setting. You definitely don't want to set the token in the separate process, it would be better to set some shared store with the value and have your main process read that. If you do try and set from a different process and get some strange behavior, please feel free to share and I can look into whats going on further with a dummy application or logs.

[github-actions]

This issue is stale due to inactivity. Please let us know if you are still encountering issues, otherwise this issue will automatically close in 10 days.