moving-bits
moving-bits
> Is this issue solved meanwhile (by @moving-bits changes mentioned above)? The original issue is resolved, but I'm unsure about the things mentioned in https://github.com/cgeo/cgeo/issues/15452#issuecomment-2000581254
My plan was to create a feature release from `release` either tonight or tomorrow, as discussed in our last dev meeting.
> i have no idea whether there's a delete function in c:geo. it's just that I'm aware of those API changes and wanted to communicate those findings. ok, thanks for...
retest this please
failing tests are unrelated, reason for failure is CAPTCHA problem during tests
> @moving-bits thx for rebasing it on top of release. Now we need to apply @murggel 's one line change to ALApi, however, I am away from my dev system...
Starting a new attempt for releasing c:geo after updating the foreground services declaration: - [x] Check/insert correct version name in `BranchDetectionHelper.java` - [ ] Wait for a Crowdin cycle or...
Last build got rejected again, this time with different services being marked as wrong - one of those services had been accepted in earlier builds... 🤔 Starting a last try...
Starting another attempt, this time for a beta version: - [x] Wait for a Crowdin cycle or trigger sync manually - [x] Merge the related Crowdin translation pull requests for...
FYI: Looks like the newest beta (2024.08.31-RC) passed their tests. 👍 I'll wait until Play Store provides this update, then send notification via CI and prepare a regular release with...