Issue with Clarifai

[vigzmv]

Clarifai has recently switched to API Keys replacing Access Tokens/Client ID & Secret. Read about it here.

Access Tokens/Client ID & Secret can no longer be created. Clarifai only issues API keys now. But the new API key feature isn't completely compatible with the clarifai javascript client yet.

Hence those who want to build this themselves have to wait till clarifai fixes this issues. (And also this issue with react native). This is really frustrating.

However you can get the signed release apk for android from here to try it.

[maxcell]

Howdy @vigzmv! You are absolutely right that we have switched to API Keys and will be ensuring that users switch over to API Keys, but I am curious on where you find the incompatibility issues with them currently? One of the important differences with API Keys is that you can limit your scopes to what calls one can make, so if you are having issues with the API keys, then I would say check your scopes and see if those give you any problems!

We are working on the React Native issues as you speak though 😄. We appreciate everyone's feedback and making sure that not only our product but our clients get taken care of.

[vigzmv]

Thanks for reaching out @maxcell!

One of the issue was with asap, which obstructed the usage of clarfai with react-native, it has been fixed in asap 2.0.6.

Yes the API keys feature is definitely a plus over the old method. But I wasn't able to use clarifai 2.2.0 with API keys, I will get back here with the exact issue that I was getting.