search

QuickBlox / quickblox-ios-sdk

QuickBlox iOS SDK for messaging and video calling
https://quickblox.com/developers/IOS
MIT License
397 stars 358 forks source link

Reset Password not working #1218

Closed sohaibkhaa closed 4 years ago

sohaibkhaa commented 4 years ago

New Issue Checklist

Environment details

Info Value
iOS Version e.g. 8.0
Quickblox iOS SDK version e.g. 2.7.6
QuickbloxWebRTC SDK version e.g. 2.2.1
Xcode Version e.g. Xcode 8.1
Repro with our demo sample e.g. does it happen with our demo sample?

Did this work before? Not

Expected behavior

Actual behavior

Logs

Please use the following template for logs:

To enable full logs use the following code:

[QBSettings setLogLevel:QBLogLevelDebug];
[QBSettings enableXMPPLogging];
Title for logs ```logos // === REQUEST ==== 9c4545be-9ce1-44f4-835f-fecf441ee920 === REQUEST GET https://api.quickblox.com/users/password/reset.json HEADERS QuickBlox-REST-API-Version=0.1.1 QB-SDK=Android 3.9.2 QB-Token=7e789a725749d2f6bc6c4de79924b6e758013ad6 PARAMETERS email=awais@gmail.com INLINE GET https://api.quickblox.com/users/password/reset.json?email=awais%40gmail.com D/EGL_emulation: eglMakeCurrent: 0xe8769920: ver 2 0 (tinfo 0xe86f4890) D/EGL_emulation: eglMakeCurrent: 0xe8769920: ver 2 0 (tinfo 0xe86f4890) D/EGL_emulation: eglMakeCurrent: 0xe8769920: ver 2 0 (tinfo 0xe86f4890) D/EGL_emulation: eglMakeCurrent: 0xe8769920: ver 2 0 (tinfo 0xe86f4890) D/EGL_emulation: eglMakeCurrent: 0xe8769920: ver 2 0 (tinfo 0xe86f4890) D/QBASDK: ********************************************************* *** RESPONSE *** 9c4545be-9ce1-44f4-835f-fecf441ee920 *** STATUS : 403 HEADERS Status=403 Forbidden Transfer-Encoding=chunked Server=nginx/1.16.1 Access-Control-Allow-Origin=* X-Request-Id=e65ae5fc-aa28-4668-9ea1-6892fc97940f X-Content-Type-Options=nosniff X-Runtime=0.015882 Connection=close X-Android-Received-Millis=1591366754506 Date=Fri, 05 Jun 2020 14:19:14 GMT QuickBlox-REST-API-Version=0.1.1 X-Frame-Options=SAMEORIGIN X-Android-Selected-Protocol=http/1.1 Strict-Transport-Security=max-age=31536000 Cache-Control=no-cache X-Android-Response-Source=NETWORK 403 Set-Cookie=_mkra_ctxt=b6f4b965749624ef331972094073a8f1--403; path=/; max-age=5; HttpOnly; secure X-Android-Sent-Millis=1591366754213 X-XSS-Protection=1; mode=block QB-Token-ExpirationDate=2020-06-05 16:08:42 +0000 Content-Type=application/json; charset=utf-8 BODY '{"errors":["User does not have a confirmed email address"]}' ```

Steps to reproduce the behavior

Any others comments