Mentorship-android: Bug: Mismatch mentor/mentee availability in My profile and Send Request

Created on 3 Mar 2020  路  11Comments  路  Source: anitab-org/mentorship-android

Describe the bug
I created 2 users, user A available as Mentee only and user B available as Mentor only. When I login as user A and tried to send request for B to be my mentor, I've got error saying 'both users are only available to mentor'. This bug does not exist in the reverse scenario (when I login as B try to send request to A to be my mentee).

To Reproduce
Steps to reproduce the behavior:

  1. Create 2 users, A available to mentee only the B available to mentor only
  2. Login as A and try send request to B to be mentor
  3. You'll get an error saying both of you are only available as mentor

Expected behavior
It should not be a problem as A is not available to Mentor

Screenshots

user A profile

Screen Shot 2020-03-03 at 11 46 08 am

error message when sending request to B
Screen Shot 2020-03-03 at 11 45 39 am

Smartphone (please complete the following information):

  • Device: Pixel 2 API 27
  • OS: IOS Mojave 10.14.6
  • Version ??

Additional context
None

Coding Bug

Most helpful comment

@mtreacy002 @Priyansh-Kedia I will leave this issue open then :) I really appreciate you two not overcommitting and updating here that you will not work on this issue. So thank you !

All 11 comments

May I work on this issue?

@mtreacy002 I have no idea why this may be happening. This seems like a really good catch, so thank you for reporting this 馃帀 If you wish to work on this, then go ahead. This sounds like an issue from Backend side, right? If yes, can you please create an issue there and refer to this Android issue there?

@mtreacy002 I have no idea why this may be happening. This seems like a really good catch, so thank you for reporting this 馃帀 If you wish to work on this, then go ahead. This sounds like an issue from Backend side, right? If yes, can you please create an issue there and refer to this Android issue there?

Thanks, @isabelcosta. Ok, I will create issue there and start working on it. 馃憤

May I work on this issue?

@Priyansh-Kedia, is it ok if I try to work on this issue first? If I feel lost in the process, I will definitely ask your help. 馃槈

@mtreacy002 Sure, I'd be happy help.

@Priyansh-Kedia, I might take some time off from this coz I need to start my GSoC20 proposal 馃榾. Are you still available to work on the issue? If not, I will open it to everyone on Zulip. But the PR might need to be submitted through backend repo if this is a backend related bug. I have opened an issue at backend (issue #477.

@mtreacy002 Thanks for the opportunity, but at this time I have taken up multiple issues myself.
I might not be able to take this up right now.
Thanks.

@mtreacy002 @Priyansh-Kedia I will leave this issue open then :) I really appreciate you two not overcommitting and updating here that you will not work on this issue. So thank you !

Hi @isabelcosta, I found the bug. It's in the Android UI, not at backend #477. Can I please send the pull request?

Sorry, still have to find the bug first. I'll work on it if it's ok with you... maybe i'll start tomorrow, need a good night sleep 1st for now... 馃槂 馃槾

Hi @isabelcosta . I've fixed the bug.. Gonna push the PR now. 馃槈

Was this page helpful?
0 / 5 - 0 ratings

Related issues

epicadk picture epicadk  路  5Comments

isabelcosta picture isabelcosta  路  6Comments

mohak1283 picture mohak1283  路  9Comments

vaishnavi-29 picture vaishnavi-29  路  3Comments

annabauza picture annabauza  路  7Comments