Support IHateMoney QR codes

[magshee]

Closes #90

This required a little more work than I had expected, but I’m really happy to made progress in this PR.

Here are the changes:

• IHateMoney QR codes contain a PROJECT_TOKEN that can be used a as Bearer token for authentication. For some reason, the project identifier was stored in a variable called token. I decided to store the project identifier in a new field and use the token variable for the IHateMoney token.
• I wanted to keep the existing functionality of adding a IHateMoneyProject via project identifier and password. And since Cospend QR codes also still provide these information instead of a project token, I chose to replace the usage of Tupels with actual data types that differ, depending on whether password or access token was used.
• IHM projects can also be added by pasting the invite link via paste button

Thoughts for further consideration:

• Some blocks of code (i.e. in AddProjectQRViewModel were already commented. If they are not used/required, maybe consider removing them
• What is missing is the possibility to create a QR to share a IHateMoney project. This is currently only supported for Cospend projects.
• Do you have any idea, what a MoneyBuster string is? I opened MoneyBuster and shared a project, and got a regular (not masked) project link

Eventually there are still things in here that can be improved, looking forward to your feedback!

[InteractionEngineer]

Thank you very much for the extra effort, I'm happy to see it working now!

Unfortunately, during testing I finally got "the too many requests error" with my own cloud (no matter your new feature changes or my previous attempts to fix #81). I'd like to look into this first before continuing reviewing and testing you changes. A bit tight on capacity right now, but I'll try my best!

[magshee]

Thank you very much for the extra effort, I'm happy to see it working now!

Unfortunately, during testing I finally got "the too many requests error" with my own cloud (no matter your new feature changes or my previous attempts to fix #81). I'd like to look into this first before continuing reviewing and testing you changes. A bit tight on capacity right now, but I'll try my best!

No worries, take your time!
Let me know when i should update my branch. The PR #94 already looks promising. I hope you finally got it fixed!

[InteractionEngineer]

Hi @magshee and happy WWDC! I catered to two issues seemingly more severe first and gladly none of those fixes touch any file you changed, so I'll be able to review and test your code regardless of that.

This is next on my list and I'm sorry it took so long, still – or even more so, I really appreciate your contribution and will try my best to merge it soon. Then it becomes time to push all the latest improvements to the AppStore. Liquid Glass will also be mandatory from Xcode 27 onwards, so that's another small exercise before getting the update out there. But also a great opportunity for some UI fixes I honestly feel more at home with. 😄

[InteractionEngineer]

Thank you for your patience! I am thrilled about the new functionalities, thanks for your work! I've had a look on the changes and left some comments that came to my mind – sorry, I fell back to German with those.

Regarding MoneyBuster: Unfortunately I don't have access to Android systems and assumed it must be a deep-link, like in iOS that opens within an app directly. If you see MoneyBuster works differently, please feel free to adjust our code.

One last important bit: Changing from token to projectId, or rather adding it and alter the previous token duty might / will affect historic app data. Were you able to test migration and see effects on projects added before your update? I confirmed it'll work really well with a blank database.

[magshee]

Thanks for your feedback! I'll address the last comment at some point in the next days!

[magshee]

One last important bit: Changing from token to projectId, or rather adding it and alter the previous token duty might / will affect historic app data. Were you able to test migration and see effects on projects added before your update? I confirmed it'll work really well with a blank database.

I was currently testing the migration and stumbled upon a problem. I thought I had already done a successful test a few weeks ago, but this might only be with a cospend project. I'll let you know as soon as I could verify that both existing Cospend and IHM projects are sill working. It might take me a couple of days though, but thanks for your patience!

[InteractionEngineer]

I was currently testing the migration and stumbled upon a problem. I thought I had already done a successful test a few weeks ago, but this might only be with a cospend project. I'll let you know as soon as I could verify that both existing Cospend and IHM projects are sill working. It might take me a couple of days though, but thanks for your patience!

Thanks for your endurance and I'm really glad we caught it so early!