Hi, I got the app update last night and was asked to take a screenshot and send it to the dev, so here it is
Awesome, @Sylvia, thank you for posting this!
Pleased to mention that @pabloscloud said that their scrolling issue was resolved today, handled by one of the fixes associated with v1.2.1
. Also, we have a new release queued up:
Release v1.2.2
The new login associated with our migration off of Wordpress routes us through a new URL (https://id.resonate.coop) for login in the player, Iâm adding that new URL to our list of allowed in-app URLs, so users can once again log in in stream-app
. Iâm submitting the new release to app stores, pending review people from Google/Apple, the update should be available in the next 4-48 hours to everyone (itâs available immediately for those able to install binaries on their mobile devices here).
Delighted to share that the âLearnâ menu dropdown being non-functional for iOS is FIXED on the production server! To be clear, this fixes the menu and allows full functionality for mobile/iPad iOS users in all browsers and for iOS stream-app
users.
Weâve also been pushing out a bunch of other fixes for the player (which also fix things for the mobile app) just to handle things associated with the transition off of WordPress. Special thanks to @auggod and @psi for all of their hard work on this.
Youâre wonderful, Iâll give this a try when I can.
A couple of updates:
- Allowed iOS users to use the Learn dropdown on the ID server, anytime a user visits any page on https://id.resonate.coop on iOS, be it in the stream-app or their mobile browser, the âLearnâ dropdown should now work as intended.
- Made some headway on the Resonateâs new mobile app - we can now play/pause, skip, rewind through tracks on a test playlist on the new mobile app (not yet available in app stores). This is still very preliminary (UI will change a great deal) but this is really exciting. Because we wonât be bound to the web playerâs functionality anymore, weâll be able to do fancy things like push notifications on new music releases (if the user wants them) and other similar things that can probably really boost community engagement.
Hello everyone! Weâre running into an issue with Google Play, that we need to address by October 6, 2022 to keep the Android app online. This Google Play tester was able to navigate to this page in the Android app, on what appears to be a tablet, and was able to open the Open Collective contribution page in-app. This shouldnât be possible because Iâve intentionally excluded Resonateâs Open Collective from our allowlist, which should force all links to this domain to open in the userâs browser (and not in our app), merely to appease these Google Play payment requirements. Hereâs a screenshot of where the tester was able to see this screen:
Iâm unable to find a way to navigate to this screen in-app or in browser. If anyone has any luck poking around in-app and can get this screen to come up, can you please post here the steps you took and the pages went to and links you clicked on to make this appear? If this screen opens in a new window / separate browser on mobile, weâll be good by Googleâs book, from what I can tell. But, if I canât reproduce the situation myself, itâs really tricky for me to try to figure out how to fix it. Thanks in advance for the help everyone! We have a couple of hundred active users for this app so it would be great to keep it up and running.
Hereâs the full report from the Google Play Store for posterity:
After a recent review, we found that your app Resonate (com.resonate.streamapp is not compliant with one or more of our Developer Program Policies. Please resolve the issue described below by October 06, 2022 or your app will be removed from Google Play.
Issue with your app
Your app contains content that doesnât comply with the Payments policy. Please see the attached screenshot for more information.Issue details
We found an issue in the following area(s):
- In-app experience: Please see attached screenshot com.resonate.streamapp-InAppExperience-357.png
About the Payments policy
Apps that employ in-store or in-app purchases must comply with the Payments policy guidelines. Specifically, Google Playâs billing system must not be used in cases where payments include tax exempt donations.Eligible developers have the following options to offer an alternative billing system in select countries for non-gaming apps:
- Offer an alternative billing system alongside Google Playâs billing system as part of our user choice billing pilot. Please visit our FAQ for more details.
- Offer an alternative billing without user choice to their users in the European Economic Area (EEA). Please visit our FAQ for more details.
Status: Further action required
Your app may be removed from Google Play if you do not resolve this issue by October 06, 2022.
Action required: Resolve this issue by October 06, 2022
To help make sure that your app stays available on Google Play:
- Read through the Payments policy for more details.
- If the donations are for an eligible tax-exempt organization, please provide verifiable documentation that indicates the organizationâs tax-exempt status (e.g., Internal Revenue Service determination letter for entities in the United States) through the Advance Notice Form.
- If the organization is not a tax-exempt organization, you must remove the donation functionality from your app or use Google Playâs in-app billing system when collecting donations.
I couldnât find any possible way to access that screen. However the screencap is v7.0.2 and Iâm at 7.1.7 and I notice that my âdonateâ button just doesnât link to anything anywhere which is where I would expect to have a link to opencollective? However since that doesnât work (it does get me out of the app though just it points me to an error 404 page) I canât find any other way to stay in app and have access to open collective.
Thanks so much for testing @LLK!
And yeah, I noticed that about the Donate link too. The fix has been merged, but updating the player on live involves manually copy pasting a local build over on the server (very tricky, would break things, tentatively impossible even?), we donât have a CI built to automate that process like we do for the newer/actively developed repos.
Google has said theyâve âacceptedâ my recent build in a review where I was slightly more strict with the allowlist, but itâs not yet obvious if that means weâre in the clear or theyâre just allowing the new build to be online until October 6. Iâll be following up with them to get details.
Update from Google:
Please note: In some instances, the warning may continue to be displayed after the review has been completed. If you successfully resolved the issue or submitted your Data safety section on Play Console, no further action is required and you DO NOT need to contact us about this warning.
So we should be once again good to go!
Small update here: Google circled back and said we arenât even allowed to link to a donation page that doesnât conform to their payment expectations unless weâre a non-profit. I petitioned and pursued routes to escalate to no avail. So our Android app is currently offline. If youâre on Android, youâll need to grab the latest release and manually install.
That being said, this isnât the biggest deal in the mid to long term. The mobile repository is under active development and will allow us to easily navigate situations like these. And Iâd like to give a special shout out and kudos to newcomer @dominictwlee who has helped out on mobile this week!
Minor update: @dominictwlee has added preliminary home screen UI to mobile
.
Hereâs a short and sweet video demonstration (again, all this UI/UX stuff is in its early stages, goal is to get functionality and features in place first and improve the look and feel later):
https://drive.google.com/file/d/1kZ7R8kUdIL7KmTrXELHMiBh8OktorVLO/view?usp=share_link