Some times payment connection callbacks trigered multiple times.
When we request a connection to the SDK, if the initial method of connection (service connection) fails, the callbacks are triggered. This means that the SDK is unable to connect to the market, and the app developer assumes that the connection request has failed and is completed. However, in the background, the SDK continues to attempt to connect using another method. Suddenly, another set of connection callbacks is triggered, which disrupts all the calculations made by the developer.
Reference Issues/PRs
None
What does this implement/fix?
Some times payment connection callbacks trigered multiple times. When we request a connection to the SDK, if the initial method of connection (service connection) fails, the callbacks are triggered. This means that the SDK is unable to connect to the market, and the app developer assumes that the connection request has failed and is completed. However, in the background, the SDK continues to attempt to connect using another method. Suddenly, another set of connection callbacks is triggered, which disrupts all the calculations made by the developer.
Any other comments?
No