-
Notifications
You must be signed in to change notification settings - Fork 19
Profile API: Fails with certain tags #10
Comments
Found another profile with same error: |
Another one: http://api.cr-api.com/profile/RC92GVLG @selfish this might be a bug now — though I don’t know how you would solve this… |
Found these profiles with the same bug: http://api.cr-api.com/profile/8yy2yjjyc |
I have added better error reporting in order to gain insight on this issue. |
Turned out to be easier than I expected. @smlbiobot @Gr8z, thank you guys for your input, this was very helpful! |
These profiles are still giving errors: Although, most of the other profiles are working now. |
Fix caused instability. |
Partially fixed. Still investigating. |
I've searched for this code (8220RQ9Y) and I can not find it anywhere, are you sure the profile exists? |
@SOSkr, thanks for the input. Perhaps this one is a mistake. Bottom line, until I can cofirm that all errors are gone, I'll keep investigating. |
Still seeking reason for parse failure with: |
Failing with: |
Failing with: http://api.cr-api.com/profile/2YRQPRGG also guys: please don’t wrap your URLs in code escape coz it would be nice to be able to click on them 😉 @Gr8z |
What code escape 😛 |
… |
I actually escaped them because I need to copy them and I don't want then accidentally clicked 😂 |
@roncho12 I tested most of those URLs, almost all of them returned a 200. Not sure why you are getting 520s |
Hi, some help please! With other works great. |
http://api.cr-api.com/profile/8VRJ02QJP |
Here is another tag that returns the wrong user # 92GQJLVC0 |
How can this be an invalid tag if the user has this in the game? |
@jmibegi2h its not invalid, but the issue is the API return data for the tag #8U2UVRPJ when you call the tag #92GQJLVC0 and thats the issue reported. |
something has become so many cases when it returns Incorrect information about the tag! Here's another # 9YOLJP8LQ that can be fixed at all? |
#98C2R0CRP |
Whoever logged stuff around here, I believe this issue is fixed. Fixed in v6.0.0, closing. |
This is a very odd issue. The API currently fails to fetch specific profile tags even though I have verified that their tags are correct.
Example:
http://api.cr-api.com/profile/LVJCL0
This member is currently in Reddit Echo:
http://api.cr-api.com/clan/LGVV2CG
And the clan api also reported his tag:
He has also verified that it is indeed the same tag on his profile.
This just might be those unfixable bugs…
The text was updated successfully, but these errors were encountered: