ConnectSDK-Android icon indicating copy to clipboard operation
ConnectSDK-Android copied to clipboard

Unable to Reconnect with skipConfig = true After Connecting and Disconnecting via Connect Button Without Enabling Any Triggers or Actions.

Open nikhil-ilumi opened this issue 5 months ago • 5 comments

Steps to reproduce

  • Click the Connect Button with skipConfig = true, providing a valid token and email.

  • On the first attempt, it redirects to the IFTTT app to connect using the user’s IFTTT account, then returns to your app.

  • At this point, the configuration is pending (no triggers or actions are enabled).

  • The user then disconnects the connection using the Connect Button.

  • Now, when attempting to connect again using the Connect Button with skipConfig = true,

  • The connection fails every time

nikhil-ilumi avatar Jul 18 '25 04:07 nikhil-ilumi

Thanks for reporting the issue. Just to make sure I understand it correctly, the first attempt was successful and the state that the connection was in, pending configuration, was expected; the issue is on the future attempts to enable the connection, after disabling it. Is that right?

If so, do you have an example connection that I can test? You can just tell me the connection id. Another thing to try to isolate the issue is to try this flow again, but without the IFTTT app installed.

lzanita09 avatar Jul 18 '25 14:07 lzanita09

Hi,

Thanks for quick reply!

Yes, your understanding of issue is correct. The issue is on future attempts to enable the connection after disabling it and only if the connection is in pending configuration (Only when No trigger/Actions are enabled).

Here is a connection ID you can test with: XxktDaTQ

Also I have tested the flow without IFTTT app installed and it is having issue with that flow as well.

nikhil-ilumi avatar Jul 21 '25 04:07 nikhil-ilumi

The connection fails every time

Could you describe a bit more about how it fails?

lzanita09 avatar Jul 21 '25 16:07 lzanita09

After disconnecting, when I click the connect button again, it shows “Connecting…” for a while, but then nothing happens and the button goes back to showing “Connect”.

nikhil-ilumi avatar Jul 22 '25 03:07 nikhil-ilumi

From our logs, it looks like this might be a backend issue, that we will try to fix there.

lzanita09 avatar Jul 22 '25 15:07 lzanita09