Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'initializeForExtension(withConfig:)' is unavailable in iOS #841

Open
emirua opened this issue Dec 12, 2024 · 1 comment
Open

'initializeForExtension(withConfig:)' is unavailable in iOS #841

emirua opened this issue Dec 12, 2024 · 1 comment

Comments

@emirua
Copy link

emirua commented Dec 12, 2024

SDK version: 3.6.0

Are logs available?
Not needed, error at build stage

Describe the issue
I'm migrating to the new version using pods, but this is not documented explicitly so I'm not sure if I'm doing it correctly, but I really think it should be right. The problem is that I'm getting an error saying that the method 'initializeForExtension' is not available for iOS and this might be an error in the library since it looks like the method is marked to not be available for iOS.
Do I have to change something in my NotificationServiceExtension to make it work?
My build was working fine in the previous version.

Screenshots

This is how I'm implementing the pods in NotificationService:
image

This is the error that is showing when I'm trying to build:
image

Method in the library marked as unavailable in iOS:
image

@mahmoud-elmorabea
Copy link

mahmoud-elmorabea commented Dec 13, 2024

Hi @emirua

Sorry to see you are running into a problem with the migration!

I created a new app from scratch and added a rich push extension target using steps in the docs and was able to add the code snippet and build the project successfully.

To be able to help further figure out what could be going wrong with your setup:

  • Can you please make sure that you are setting up the notification service extension correctly cause this error might suggest that you are not utilizing it in a extension but rather in a different target
  • Please provide more info about your setup since the screenshots are only showing partial parts of the config, it would be ideal if you can replicate the issue in a minimal project sample and provide us with that

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

No branches or pull requests

2 participants