Accountability Partner feature doesn't work

[vibhor1102]

The application never requests SMS permission, and shows up "SMS permission denied" regardless. And it's not something I can manually assign from the settings.

[HumbleBee14]

Thanks for pointing this out. This is actually intentional rather than a bug, since Google Play does not allow certain apps with the SEND_SMS permission to be published, so I had to disable it to pass their review.

The functionality is still there, it's just a single line of code that needs to be uncommented. If this feature is needed, we can release the full version through third-party APK providers that allow these permissions.

[vibhor1102]

If this feature is needed, we can release the full version through third-party APK providers that allow these permissions.

Maintaining a separate distribution channel, through GitHub releases or F-Droid could be something you could look into, and with a high VersionCode and same package name, signature, etc. it could be feasible to allow the other distribution channel's application to cleanly update over the Play Store's copy, and with GitHub actions or Gradle product flavors, the dual channel release could be automated, at least to some extent.

Do consider some approach for dual distribution channel for the future, whenever you spare some time back for this project.

@HumbleBee14

[HumbleBee14]

@vibhor1102 I have enabled dual flavors in the release mode. Now, not via playstore, each release will generate SMS variant apk also in each release.
https://github.com/HumbleBee14/ZenLock/releases/tag/v1.10.0

Hope this helps!