question

I think I may have found an issue.

If the app has not been installed, and I make a call to https://sandbox.dev.clover.com/oauth/v2/authorize, Clover takes me to the App Marketplace where I see my app and I can click the "Connect" button. Unfortunately, when I click the "Connect" button, I think that Clover sends the "old" access code back to my app, and making a request to oauth/v2/token with that access code fails.

BUT... now that the app is installed in Clover, if I make a call to https://sandbox.dev.clover.com/oauth/v2/authorize again, it skips going to the marketplace (because the app is already installed) and redirects back to my app with the correct access code and my call to oauth/v2/token is successful.

This seems to be a bug. Please correct me if I am wrong, but I cannot get an access and refresh token unless the app is already installed, which means I have to click that "Connect" button in Clover to install the app, fail in my app, then make the call to authorize again. Not very ideal.

Can someone at Clover please take a look at this? My customers are not able to authenticate when clicking on the connect button in the app marketplace. But once the app is installed, they can go successfully from my app to clover and authenticate. My suspicion is that I am using the new CORRECT authentication, and the connect button in the marketplace is not. Maybe I am wrong, but I cannot figure out why my customers cannot authentication when going to my app from the marketplace.

Is anyone at Clover taking notice of this issue? Does anyone in the development community experience the same thing? How do I get support from Clover to at least acknowledge the issue, or give me a hint as to what I may be doing wrong, although I am pretty certain that I'm not doing anything wrong.