awesome_notifications causing problems with iOS

[cool2apps]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

With parse_server_sdk_flutter package version 5.1.0, awesome_notifications becomes a dependency and awesome_notifications causes compile errors when building iOS apps.

Feature / Enhancement Description

Is it possible to use parse_server_sdk_flutter package without any notifications package? For example if you don't want to use any notification features with parse server, than you don't need to add any notification package to your project. If you want to use notification features with parse server, than you can manually add awesome_notifications package as a dependency to your project, manually.

If it has to be added a notification package, is it possible to use flutter_local_notifications instead of awesome_notifications, which is easier to integrate with iOS.

Example Use Case

Not applicable.

Alternatives / Workarounds

None. I can't manage to compile iOS apps with awesome_notifications.

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[mbfakourii]

If possible send the errors

Is this your problem?

[mtrezza]

I think it could make sense to make the notifications package optional. There are other notification providers that one could use, so they don't need that dependency, but it should be available OOTB for convenience. Would it be possible to make this an optional module (not sure if Flutter has such a concept), like for example the optional adapters in Parse Server?

@cool2apps, could you please provide more details about the compile errors?

[cool2apps]

If possible send the errors

Is this your problem?

Yes.

[cool2apps]

I think it could make sense to make the notifications package optional. There are other notification providers that one could use, so they don't need that dependency, but it should be available OOTB for convenience. Would it be possible to make this an optional module (not sure if Flutter has such a concept), like for example the optional adapters in Parse Server?

@cool2apps, could you please provide more details about the compile errors?

These are the error messages. But I will send detailed compile errors later today. When I change minimum OS to iOS 13, then I get other errors.

On the other hand, if I can manage to compile by increasing to iOS 13, I don't want to increase minimum iOS version from 11 to 13, when I don't need notifications.

[!] CocoaPods could not find compatible versions for pod "awesome_notifications":
  In Podfile:
    awesome_notifications (from `.symlinks/plugins/awesome_notifications/ios`)

Specs satisfying the `awesome_notifications (from `.symlinks/plugins/awesome_notifications/ios`)` dependency were found, but they required a higher minimum deployment target.

[mbfakourii]

I think it could make sense to make the notifications package optional. There are other notification providers that one could use, so they don't need that dependency, but it should be available OOTB for convenience. Would it be possible to make this an optional module (not sure if Flutter has such a concept), like for example the optional adapters in Parse Server?

@cool2apps, could you please provide more details about the compile errors?

It seems that this problem has been solved in
awesome_notifications pre-release version 0.7.5-dev.2+1

In my opinion, there is no need to make this optional, the problem is only in a certain package

[mtrezza]

Still, developer may want their own push notifications systems, that's common in Android, iOS. So I wonder whether this can be made optional to provide a lighter core package?

In broader terms, the SDK may benefit from a modular structure like our other SDKs where developers can choose to not install certain modules they don't need.

[cool2apps]

If possible send the errors

Is this your problem?

I still have this problem.

Here is the actual error messages I get:

Failed to build iOS app
Swift Compiler Error (Xcode): Using bridging headers with module interfaces is unsupported

Uncategorized (Xcode): Command SwiftDriver emitted errors but did not return a nonzero exit code to indicate failure

Encountered error while archiving for device.

I have tried a lot of combinations like awesome_notifications 0.7.5-dev.2+1, latest development version awesome_notifications: ^0.7.5-dev.3, changed to minimum target to iOS 13, revert back to iOS 11 (which latest development version does not require iOS 13). I get similar error messages and I failed to compile at iOS.

So I switched back to parse_server_sdk_flutter: ^5.0.1 to be able to compile it at iOS.

[mbfakourii]

Temporarily use the following method to release the new version of awesome_notifications

dependency_overrides:
  awesome_notifications: ^0.7.5-dev.3

[mtrezza]

Couldn't we upgrade the dependency in the Parse Flutter SDK?

[cool2apps]

Temporarily use the following method to release the new version of awesome_notifications

dependency_overrides:
  awesome_notifications: ^0.7.5-dev.3

I got the same error with this dependency override.

[cool2apps]

By the way, I noticed that according to parse server SDK documentation, parse_server_sdk_flutter package is not compatible with flutter 3.10. And I was using flutter 3.10.5 when I get those error messages.

[cool2apps]

But to use Awesome Notifications FCM on release mode without the watermark [DEMO], you need to purchase a license key.

Awesome Notifications FCM plugin is not free and need to be paid to have an app without a demo watermark.

Please make parse_server_sdk_flutter package Awesome Notifications free. Notification package should be optional and should be choosable by the developer of the project. At my previous project, I implemented notifications with parse_server_sdk_flutter, flutter_local_notifications and firebase_messaging packages free and without any watermark and working fine.

[mbfakourii]

But to use Awesome Notifications FCM on release mode without the watermark [DEMO], you need to purchase a license key.

Awesome Notifications FCM plugin is not free and need to be paid to have an app without a demo watermark.

Please make parse_server_sdk_flutter package Awesome Notifications free. Notification package should be optional and should be choosable by the developer of the project. At my previous project, I implemented notifications with parse_server_sdk_flutter, flutter_local_notifications and firebase_messaging packages free and without any watermark and working fine.

If possible, test this

dependency_overrides:
  awesome_notifications: ^0.6.21