Troubleshooting - AEVI-AppFlow/pos-android-sdk GitHub Wiki

If you are having issues with integrating AppFlow, this section may help you to troubleshoot it.

General

AppFlow provides two main mechanism for on-device troubleshooting. The AppFlow Overview provides System audit logs which contains information about the state of the system, incl whether any flow services were rejected, any failed initiation calls, etc. This is a good starting point to see what is going on.

In addition, there are audit logs per request, in the Request history view. From there you can see what happened during a flow and why a flow service may not have been called, etc.

Initiation

If you are having problems calling the APIs, there are a few steps you can follow

  • Are you handling any errors properly? By handling errors, you should get an error code back outlining the issue
  • If you are not getting errors back, have a look at the System audit log in AppFlow Overview on the device to see if it provides any details
  • Make sure the Flow Processing Service (FPS) is installed on the device

Flow services

If your flow service is not getting called, there are a few possible causes to investigate.

First, check if your application is listed under Flow services in AppFlow Overview. If not, it points to an issue with how your application is exposing its API entry points. Double check that you are using the correct intent actions, etc in the manifest.

If your application is listed, then it may be due to;

  • Your application is not defined in the flow. If you are using the Developer Config Provider, open it and view the relevant flow and from there you can add your app to the relevant flow
  • Your application does not support the stage that it is defined in the flow for. Check intent actions and what methods you are overriding in your service class.
  • Your application is using a different major API version to the flow processing service - check the logs
  • Missing flow type support - have you listed the flow type that is being used as supported via your PaymentServiceInfoProvider implementation?
  • Unsupported currency - have you specified supported currencies? If so, maybe the current request is using a different currency.