Closed firefoxlover closed 2 weeks ago
@firefoxlover it is à new baby app based on the same code. It is to handle cards Both will be released under the same repo but with different releases name
At least rename the files appropriately.
@kvmgithub what s that screenshot? The apps are named correctly. Everything is separated
It is Obtainium. And no, the apps are all named app-arm64-v8a-release.apk, app-armeabi-v7a-release.apk or app-x86_64-release.apk.
@kvmgithub you are talking file name, and those should not be an issue. The apps are named correctly. The issue is with Obtainium not supporting monorepo. Every single release is seen as a new app release. Opening an issue there
Every single release is seen as a new app release.
Well, even Github is showing the latest tag only for card wallet. Thanks for opening the issue though.
@kvmgithub about github latest tag, yes you are right and it is the same for all monorepo. Nothing i can do about this.
@firefoxlover As a workaround you can put "OSS Document Scanner" to the field "Filter release title" in the config in Obtainium.
@SanskritFritz @kvmgithub seeing it uses a regexp event Scanner
is enough.
I could add a note in the readme
@SanskritFritz I tried filtering by release title or notes before, that resulted in the right picture in my first comment. This time it worked.
Yeah same here, it now gives me constant "no version found" errors.
@farfromrefug I appreciate your app but releasing 2 apps in the same releases leads to confusion with likely a lot of apps. Especially as the .apk files are named the same.
@firefoxlover just tested with obtainium latest and it works fine here. I see my 2 apps correctly. Now about the naming i understand your point. But it is also very important to note that it is 100% easier for me to releases those apps that way. Which means i can spend more time on features (dont forget i am not paid, very little donations, for all that i do) and bug fixes. As for the file name. I will look if i can change that, however i am far from the only one using those names (default build names) https://github.com/zhanghai/MaterialFiles/releases
@farfromrefug I will try adding it again, maybe that helps.
The app name is not a problem. Obtainium just uses the Github metadata for the app name I guess and uses the latest tag for releases.
Ok I tried it again. When adding the app new it detects the latest APK and automatically switches to this CardWallet.
@firefoxlover Do what is shown left to get what is shown right.
I agree with @firefoxlover that this is very confusing. No one uses the same, solitary repo for multiple projects. It's not that difficult to setup another repo and build process. I don't need or want a card scanner.
You're going to drive people away from the project by doing this. I'm receiving GitHub notifications that a new version of OSS document scanner is available and then find out it's this. Please separate into 2 repos.
@exstntlmsnthrp Sorry you dont like it. But i wont change it. And please dont say it is not difficult when you dont know the implications. Obtainium is 100% capable of handling both apps as explained in this thread.
@farfromrefug I didn't say anything about obtanium.
If the implications for you are so onerous, why not explain them to the public? Then maybe people might be a little more understanding. Otherwise it just looks like lazy development practices, because you can't be bothered.
@exstntlmsnthrp Ok so github notifications yes you will get one for each cardwallet release. Maybe you can filter them i dont know. Now about the implication it is easy:
Will think about other benefits. But appart from the notification issue which appeared in this thread i dont see any other drawback. So i dont see any reason to change the way it is right now
@farfromrefug I'd just like to say thanks for taking your time to share this very thorough explanation. Much appreciated.
I better understand where you're coming from and the decision you've made regarding this.
Thank you.
Version
The release 3 hours ago has a different name. Is this wanted or in the wrong repo?
It has a different app name which causes trouble.
What platform are you using?
No response
OS Version
A
What happened?
A
Relevant log output
Code of Conduct