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

fix(expo-plugin): add check for existing service in AndroidManifest for notification controls #4172

Conversation

aminmeshk
Copy link
Contributor

Summary

This PR fixes a minor issue with Expo Config Plugins (the one related to notification controls) that caused having duplicate <service> tags in the generated AndroidManifest.xml file when running non-cleaning npx expo prebuild multiple times.

Motivation

Fix this issue: #4167

Changes

I added a check in withNotificationControls.ts file for existing service in to avoid having duplicate code in AndroidManifest.xml.

Test plan

@aminmeshk aminmeshk changed the title fix(android): add check for existing service in AndroidManifest for expo plugin for notification controls fix(expo-plugin): add check for existing service in AndroidManifest for notification controls Sep 14, 2024
@freeboub
Copy link
Collaborator

Looks easy :) Thank you for the patch !

Co-authored-by: Seyed Mostafa Hasani <seyedmostafahassani@gmail.com>
@seyedmostafahasani
Copy link
Collaborator

@aminmeshk
Would you please fix the lint errors?

@freeboub
Copy link
Collaborator

@aminmeshk
Would you please fix the lint errors?

You miss the spaces in your proposal... I commit it without thinking of it 🙄

@aminmeshk
Copy link
Contributor Author

I fixed the spaces

Copy link
Member

@KrzysztofMoch KrzysztofMoch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@KrzysztofMoch KrzysztofMoch merged commit 0538b3b into TheWidlarzGroup:master Sep 17, 2024
2 checks passed
@aminmeshk aminmeshk deleted the fix/expo-plugin-notification-service-duplicate branch September 17, 2024 12:25
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.

4 participants