I think everything is good to go, implemented things:

1. Each card on the LoyaltyCardEditActivity has a archive button, black when unarchived and white when archived
2. After long press in 1 or more cards in the overflow menu you can archive/unarchive cards
3. Archive icon in archived cards

I have no clue what Google is smoking this time, this seems like complete bullshit, and we've been using this title for years.

Looking at Google Play there are other apps using very similar titles like: https://play.google.com/store/apps/details?id=com.innovativeiteration.rewardsapp

"Reward Cards : The Card Wallet"

Why is "Catima - The Libre Card Wallet" not okay when "Reward Cards : The Card Wallet" is?

Issue by x-jokay Saturday Jan 28, 2017 at 16:26 GMT Originally opened as https://github.com/brarcher/loyalty-card-locker/issues/86

It would be great to be able to set a small picture per card on the overview.

Or even having an overview with the logo and name of the card only: https://c.mobilegeeks.de/wp-content/uploads/2013/02/stocard-04.jpg

sometimes the scanner can not scan a large size and I need to reduce the image. you can make it possible for the size to be remembered and at startup the size is already small as last time.

I'd like to contribute to this project, if I can manage to find time and learn the internals of the code, to provide an extremely useful feature for people who wanto to use this app in their daily life. Currently, I own CardMate adware app and I would like to switch to something open source. Thanks dns66 anyway.

Android 11, for thos who already got it, provides APIs to customize the Power Menu screen. Here is another interesting article.

User story. User holds the power button and the Device Controls menu is displayed. Maybe the user has Google Pay credit cards on top, or some Google Home devices. Catima will show the most favourite cards that are configured from the user interface.

In the future, the cards displayed and their order on Device Controls/Power Menu Screen could be based on other factors as well.

Issue by natrius Friday Apr 27, 2018 at 12:49 GMT Originally opened as https://github.com/brarcher/loyalty-card-locker/issues/238

Add the option to autobackup after a new card is saved.

Here it is. Linked to #146 I finally made it crapping with the Java Flow.

I succeeded in not adding RxJava as dependency, but had to upgrade to Java 11. Long press the card to open the activity.

My firewall just blocked catima.

In the description of catima it says that no Internet is required. Still, my firewall blocked internet access from catina. Another tool says that catima uses WiFi.

For what reason is catima accessing internet? And why is there no setting to disable this?

Good way to contribute for those who can't code!

Sadly, Hacktoberfest won't count commits made by Weblate. So you'll have to do it the manual way.

1. Fork this repository
2. Download Android Studio
3. Make changes with the Translation Editor
4. Create a Pull Request with your changes

Hopefully in the future Hacktoberfest will also count translations from systems like Weblate.

Note: Please only translate languages you know. Nobody likes Google Translate...

Fixes #1025

Logic was added to the ImportExportActivity to allow Catima to be associated with the following file types:

1. catima.zip
2. fidme-export-request-*.zip
3. LoyaltyCardKeychain.csv
4. *-sync.zip
5. vouchervault.json

Due to limitations that were discussed in the issue, we are only able to associate the file extensions and not the file names themselves.

The AndroidManifest.xml has been augmented to hold intent filters for these file extensions:

• .zip
• .json
• .csv

Reported to me by e-mail, apparently the gallery opens and you can select a picture, but when you come back to Catima the picture isn't there.

I can't reproduce this on my Android 11 device, so seems to be Xiaomi-specific. Need someone with a Xiaomi device to debug and fix this.

Fixes #1149

Added logic and string literal, called card_name_is_empty, to allow to show the hint in the edit text when creating/editing a card.

Translated the value to almost all languages.

As always, when you add 1 feature users will request 2 more :sweat_smile:

Got a request through email to add a "quick earn" feature. Basically the same as the current "quick spend" where it asks "How much did you spend?" but the other way around.

I'm honestly not quite sure if it's worth adding. Are there any stores that tell you you got 10 points without also telling you the total new amount of points you have? And how would this be added without getting button overload? Are other users even interested in this feature? I've never had any use for something like this myself at least.

Catima: 2.21.1 Androids affects:

• Android 9 (SDK 28)

Stacktrace:

Exception java.lang.RuntimeException:
  at android.app.ActivityThread.deliverResults (ActivityThread.java:4419)
  at android.app.ActivityThread.handleSendResult (ActivityThread.java:4461)
  at android.app.servertransaction.ActivityResultItem.execute (ActivityResultItem.java:49)
  at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:108)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:68)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1831)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:201)
  at android.app.ActivityThread.main (ActivityThread.java:6806)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:547)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:873)
Caused by java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
  at protect.card_locker.LoyaltyCardEditActivity.onRequestPermissionsResult (LoyaltyCardEditActivity.java:984)
  at android.app.Activity.dispatchRequestPermissionsResult (Activity.java:7749)
  at android.app.Activity.dispatchActivityResult (Activity.java:7594)
  at android.app.ActivityThread.deliverResults (ActivityThread.java:4412)

This Pull Request fixes #1057.

The changes are listed below.

Implemented

• Added a feature that automatically sets the front/back image with the scanned barcode. There will be a dialog shown to the users to confirm if they want to automatically set the image or not.

Code changes

• Added frontUserDefined and backUserDefined to LoyaltyCardField to distinguish if the image of the front and back card was added automatically or manually.
• Added 2 more columns(frontuserdefined and frontuserdefined) to the table of LoyaltyCardDbGroups.
• Bumped up the database version from 15 to 16.
• Added database upgrading code to migrate the database from version 15 to 16.
• Added logic code to display a dialog letting users select if they want to automatically set the scanned barcode as the front/back image of the current card.
• Added the file's URI of the scanned barcode to the intent so that LoyaltyCardEditActivity could use it to set the front/back image.
• Changed Test files to reflect the changes of DBHelper.

Potential Issues

• Might need to check if the current logic of automatic card adding is appropriate (especially for card rescanning).
• The prompted image-setting dialog may be ungrammatical or could be more concise...