Skip to content

Added example with proguard rules#26

Closed
butterbrain wants to merge 1 commit into
Rexios80:masterfrom
butterbrain:garmin_release_build_fixes
Closed

Added example with proguard rules#26
butterbrain wants to merge 1 commit into
Rexios80:masterfrom
butterbrain:garmin_release_build_fixes

Conversation

@butterbrain
Copy link
Copy Markdown

Using the example from watch_connectivity, I created a very basic example for creating a watch_connectivity_garmin flutter app (and a couple functions for the Garmin watch app itself). All in there so the user can see where to put the proguard file and create a release hopefully.

Using the example from watch_connectivity, I created a very basic example for creating a watch_connectivity_garmin flutter app (and a couple functions for the Garmin watch app itself). All in there so the user can see where to put the proguard file and create a release hopefully.
@butterbrain
Copy link
Copy Markdown
Author

Hopefully that's okay and a good basis for a merge. Not changed any code really, just pulled across your example from the base watch_connectivity and adjusted to be a Garmin watch app. Included help for the proguard settings (maybe wants including in the base watch_connectivity example if you want?)

Copy link
Copy Markdown
Owner

@Rexios80 Rexios80 left a comment

Choose a reason for hiding this comment

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

Just some quick thoughts. I will review the new example app later.

Comment thread .gitignore
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

These should be in the examples gitignore file

## Releasing (Android release build)
The app communicates with the Garmin classes via its namespace. So when released these can be minified
making them uncontactable. To prevent this from happening you will need to include the exclusions in your
`proguard-rules.pro` file as in the example:
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

This doesn't need to be in the readme. The plugin can provide these rules to consumer applications.

@Rexios80
Copy link
Copy Markdown
Owner

Closing in favor of #28

@Rexios80 Rexios80 closed this Apr 30, 2025
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.

2 participants