If I include the ACTION_START_REGISTER intent filter and my app's main activity intent filter, is that enough to have Clover call my activity when the register app is opened? Does this sound correct?No. That isn't an action that's sent when register is started, it's an action that's sent to start register. It's purpose is not to allow apps to intercept the starting of register and perform some action. If you had your filter correct, when an activity is started with that action, the result would be the system showing a chooser asking the user to select which activity to start: yours or the real register.
not only did nothing different happen when I opened the register, I have no idea how to tell that my custom intent was even attempted to be registeredIf you start register from the launcher, it's going to start it via the component so it's not going to target your app even if you setup a filter to match ACTION_START_REGISTER . I realize that's not really what you want anyway but regardless. As you can imagine, it'd be bad if an app was able to intercept the starting of other apps and replace them. E.g., imagine if I wrote an app that intercepted start Gmail and faked asking you to enter your Gmail password.
How can I debug my custom intent filter? Where do I gain visibility into what Clover is doing with my custom app?This is standard Android development here you'll find lots of resources online. Without knowing specifically what you are trying to find out it's hard to give any concrete answer.
@Jeffrey Blattman Thank you for the reply!
My goal is to:
allow your app to slot into the standard Clover payment flow
(quote taken from the Action Intents doc) I inferred from the Action Intents section of the documentation that there was maybe a way for my activity to be called prior to a built-in Clover activity (such as Register). I get your point about replacing a standard Clover activity and completely understand why I wouldn't want that to happen. I just want my activity called somewhere within the process. Is that possible?
I will "do my homework" regarding Android development - thank you for the info regarding visibility into my custom Clover app. I wasn't sure if Clover did anything non-standard that I'd need to be aware of, but based on your answer it seems the standard Android developer docs will answer all of my debugging questions.
There are many different types of intents with different meanings. There is no way to arbitrarily insert yourself in the payment flow at any point. The well-defined places you can do that are documented by ACTION_MODIFY_ORDER, ACTION_CUSTOMER_TENDER, and ACTION_MERCHANT_TENDER. These allow you to make modifications to the order and process a payment with a custom tender, respectively.
For the most part Clover development is Android development. There are some exceptions, but the handling of intents is not one of them.
3 People are following this question.