brave / brave-browser

Brave browser for Android, iOS, Linux, macOS, Windows.
https://brave.com
Mozilla Public License 2.0
17.84k stars 2.33k forks source link

"Complete" payout status is not showing green "Arrived" message banner #24980

Closed LaurenWags closed 2 years ago

LaurenWags commented 2 years ago

Description

Found while testing https://github.com/brave/brave-browser/issues/23429

When parameters endpoint returns complete (and the date is on or after the payment date), there is no green "Arrived" banner for ad grant. Green "Arrived" banner does not display until you successfully complete the captcha. This seems to indicate that the API isn't being utilized.

Steps to Reproduce

Pre-req: server should be set to return "complete" for payout status

  1. Clean profile staging env
  2. Enable Rewards
  3. View an ad and redeem it with the server (cash in your payment token)
  4. Close browser
  5. Advance date to the 6th (day before my payout day)
  6. I see the countdown banner as expected.
  7. Close browser
  8. Advance date to the 7th (or 8th, 9th, etc)

Repeat above for unverified rewards as well as verified user w/ a custodial wallet provider (Uphold, Gemini, bF)

Actual result:

No green "Arrived" banner on ads panel of brave://rewards, rewards panel, NTP widget

Expected result:

Green "Arrived" banner to show since the API is returning "complete"

Note - possibly the green "Arrived" banner should be removed from view if you complete a captcha? Mentioned by @Miyayes. Need to confirm - makes sense for it to do so in unverified case, but what happens if you have a custodian? does the banner just always display until "off" is returned from API?

Reproduces how often:

easily

Brave version (brave://version info)

Brave | 1.43.81 Chromium: 104.0.5112.102 (Official Build) (x86_64)
-- | --
Revision | 8e5396254975ef939f2ef7d0bd334e48a052b536-refs/branch-heads/5112@{#1478}
OS | macOS Version 12.5.1 (Build 21G83)

Version/Channel Information:

Other Additional Information:

Miscellaneous Information:

cc @Miyayes @emerick @GeetaSarvadnya

LaurenWags commented 2 years ago

Added QA/Blocked label until uplifted to 1.43.x

LaurenWags commented 2 years ago

Can be tested with 1.43.84 and above.

LaurenWags commented 2 years ago

Verified with

Brave | 1.43.84 Chromium: 105.0.5195.68 (Official Build) (x86_64)
-- | --
Revision | ad13e82529051bac6a0e65f455e6d7a1e5fd7938-refs/branch-heads/5195@{#903}
OS | macOS Version 12.5.1 (Build 21G83)

1. For the below cases, confirmed when "complete" is returned from payoutStatus API, and it is on or after the payout date (ex. 7th in my case), and ad tokens were cashed in for the previous month, the "Arrived" message shows as expected:

Test Case details
Unverified/Anon - PASSED When using an unverified/anon setup for rewards (no custodial provider): - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured `/parameters` API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured `payment processing` status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-07 at 8 41 28 AM | Screen Shot 2022-09-07 at 8 41 36 AM | Screen Shot 2022-09-07 at 8 41 43 AM | Screen Shot 2022-09-07 at 8 41 49 AM Logs for - `/parameters` ``` [ REQUEST ] > URL: https://api.rewards.bravesoftware.com/v1/parameters > Method: GET ........ [ RESPONSE - OnRequest ] > Url: https://api.rewards.bravesoftware.com/v1/parameters > Result: Success > HTTP Code: 200 > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.34679,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} [16048:259:0907/084118.259339:VERBOSE9:logging_util.cc(138)] [ RESPONSE HEADERS ] > Url: https://api.rewards.bravesoftware.com/v1/parameters [16048:259:0907/084118.262708:VERBOSE1:api_parameters.cc(90)] Params timer set for 13750 s ```
Gemini - PASSED - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured `/parameters` API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured `payment processing` status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-07 at 9 31 18 AM | Screen Shot 2022-09-07 at 9 31 25 AM | Screen Shot 2022-09-07 at 9 31 32 AM | Screen Shot 2022-09-07 at 9 31 38 AM Logs for - `/parameters` ``` [ REQUEST ] > URL: https://api.rewards.bravesoftware.com/v1/parameters > Method: GET ....... [ RESPONSE - OnRequest ] > Url: https://api.rewards.bravesoftware.com/v1/parameters > Result: Success > HTTP Code: 200 > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.346438,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} [2777:259:0907/093600.188197:VERBOSE9:logging_util.cc(138)] [ RESPONSE HEADERS ] > Url: https://api.rewards.bravesoftware.com/v1/parameters [2777:259:0907/093600.192604:VERBOSE1:api_parameters.cc(90)] Params timer set for 11504 s ```
Uphold - PASSED - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured `/parameters` API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured `payment processing` status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-07 at 10 09 31 AM | Screen Shot 2022-09-07 at 10 09 39 AM | Screen Shot 2022-09-07 at 10 09 46 AM | Screen Shot 2022-09-07 at 10 09 52 AM Logs for - `/parameters` ``` [ REQUEST ] > URL: https://api.rewards.bravesoftware.com/v1/parameters > Method: GET ....... [ RESPONSE - OnRequest ] > Url: https://api.rewards.bravesoftware.com/v1/parameters > Result: Success > HTTP Code: 200 > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.345569,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} [3509:259:0907/100853.240127:VERBOSE9:logging_util.cc(138)] [ RESPONSE HEADERS ] > Url: https://api.rewards.bravesoftware.com/v1/parameters [3509:259:0907/100853.242094:VERBOSE1:api_parameters.cc(90)] Params timer set for 11363 s ```
bitFlyer - PASSED - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured `/parameters` API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured `payment processing` status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Example | Example | Example | Example -- | -- | -- | -- スクリーンショット 2022-09-07 10 21 47 | スクリーンショット 2022-09-07 10 22 01 | スクリーンショット 2022-09-07 10 22 10 | スクリーンショット 2022-09-07 10 22 18 Logs for - `/parameters` ``` [ REQUEST ] > URL: https://api.rewards.bravesoftware.com/v1/parameters > Method: GET ........ [ RESPONSE - OnRequest ] > Url: https://api.rewards.bravesoftware.com/v1/parameters > Result: Success > HTTP Code: 200 > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.344985,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} [4115:259:0907/102125.483204:VERBOSE9:logging_util.cc(138)] [ RESPONSE HEADERS ] > Url: https://api.rewards.bravesoftware.com/v1/parameters [4115:259:0907/102125.486059:VERBOSE1:api_parameters.cc(90)] Params timer set for 12073 s ```

2. For the below cases, confirmed when ads are cashed in/redeemed with the server and it is prior to payout date (ex. 1st thru 6th of month depending on location), the "countdown" message is displayed in the UI:

Test Case details
Unverified/Anon - PASSED When using an unverified/anon setup for rewards (no custodial provider): - Ensured countdown message is displayed 1st-6th of month (prior to payout date, your payout date may differ): Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-01 at 11 15 30 AM | Screen Shot 2022-09-01 at 11 15 45 AM | Screen Shot 2022-09-01 at 11 15 52 AM | Screen Shot 2022-09-01 at 11 15 58 AM
Gemini - PASSED - Ensured countdown message is displayed 1st-6th of month (prior to payout date, your payout date may differ): Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-04 at 11 42 07 AM | Screen Shot 2022-09-04 at 11 42 16 AM | Screen Shot 2022-09-04 at 11 42 24 AM | Screen Shot 2022-09-04 at 11 42 32 AM
Uphold - PASSED - Ensured countdown message is displayed 1st-6th of month (prior to payout date, your payout date may differ): Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-06 at 12 00 57 PM | Screen Shot 2022-09-06 at 12 01 07 PM | Screen Shot 2022-09-06 at 12 01 15 PM | Screen Shot 2022-09-06 at 12 01 22 PM
bitFlyer - PASSED - Ensured countdown message is displayed 1st-6th of month (prior to payout date, your payout date may differ): Example | Example | Example | Example -- | -- | -- | -- スクリーンショット 2022-09-05 15 15 48 | スクリーンショット 2022-09-05 15 16 32 | スクリーンショット 2022-09-05 15 16 39 | スクリーンショット 2022-09-05 15 16 46

3. For the below cases, confirmed when "processing" is returned from payoutStatus API, and it is on or after the payout date (7th in my case), and ad tokens have been cashed in for the previous month, the processing message shows as expected:

Test Case details
Unverified/Anon - PASSED When using an unverified/anon setup for rewards (no custodial provider): - Ensured the "processing" message is shown in all expected places Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-07 at 11 17 13 AM | Screen Shot 2022-09-07 at 11 17 22 AM | Screen Shot 2022-09-07 at 11 17 30 AM | Screen Shot 2022-09-07 at 11 17 38 AM
Gemini - PASSED - Ensured the "processing" message is shown in all expected places Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-07 at 11 43 50 AM | Screen Shot 2022-09-07 at 11 43 58 AM | Screen Shot 2022-09-07 at 11 44 06 AM | Screen Shot 2022-09-07 at 11 44 12 AM
Uphold - PASSED - Ensured the "processing" message is shown in all expected places Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-07 at 12 02 50 PM | Screen Shot 2022-09-07 at 12 02 59 PM | Screen Shot 2022-09-07 at 12 03 10 PM | Screen Shot 2022-09-07 at 12 03 17 PM
bitFlyer - PASSED - Ensured the "processing" message is shown in all expected places Example | Example | Example | Example -- | -- | -- | -- スクリーンショット 2022-09-07 15 17 49 | スクリーンショット 2022-09-07 15 18 09 | スクリーンショット 2022-09-07 15 18 16 | スクリーンショット 2022-09-07 15 18 23

4. For the below cases, confirmed when "off" is returned from payoutStatus API, and it is on or after the payout date (7th in my case), and ad tokens were cashed in for the previous month, no banners display in the UI:

Test Case details
Unverified/Anon - PASSED When using an unverified/anon setup for rewards (no custodial provider): - Ensured no banners are displayed in the UI Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-09 at 11 18 40 AM | Screen Shot 2022-09-09 at 11 19 30 AM | Screen Shot 2022-09-09 at 11 19 39 AM | Screen Shot 2022-09-09 at 11 19 46 AM
Gemini - PASSED - Ensured no banners are displayed in the UI Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-11 at 11 45 36 AM | Screen Shot 2022-09-11 at 11 45 44 AM | Screen Shot 2022-09-11 at 11 45 51 AM | Screen Shot 2022-09-11 at 11 45 58 AM
Uphold - PASSED - Ensured no banners are displayed in the UI Example | Example | Example | Example -- | -- | -- | -- Screen Shot 2022-09-08 at 12 03 51 PM | Screen Shot 2022-09-08 at 12 03 59 PM | Screen Shot 2022-09-08 at 12 04 07 PM | Screen Shot 2022-09-08 at 12 04 12 PM
bitFlyer - PASSED - Ensured no banners are displayed in the UI Example | Example | Example | Example -- | -- | -- | -- スクリーンショット 2022-09-09 15 20 33 | スクリーンショット 2022-09-09 15 20 41 | スクリーンショット 2022-09-09 15 20 50 | スクリーンショット 2022-09-09 15 20 58

5. For the below case, confirmed when "complete" or "processing" is returned from payoutStatus API, and it is on or after the payout date (ex. 7th in my case), and ad tokens were NOT cashed in for the previous month, no countdown, processing, or arrived messaging shows as there is no ad grant coming for this paymentID:

Test Case details When using an unverified/anon setup for rewards (no custodial provider): - Ensured no banners are displayed in the UI Aug 30 - no ads redeemed with server | Sept 4 - no countdown banner | Sept 7 - no processing or arrived message -- | -- | -- Screen Shot 2022-08-30 at 3 52 46 PM | Screen Shot 2022-09-04 at 3 54 30 PM | Screen Shot 2022-09-07 at 3 54 59 PM

6. For the below cases, confirmed when various payout statues is returned from payoutStatus API (they're not all the same), and it is on or after the payout date (ex. 7th in my case), and ad tokens were cashed in for the previous month, the various reward types show the expected messaging:

Test Case details `{"unverified":"complete","uphold":"processing","gemini":"off","bitflyer":"complete"}` - PASSED For the above, all 4 were checked on the same day (Sept 9), all had ad tokens cashed in for previous month. Confirmed each of the above showed the expected messaging (or no messaging if "off"): Unverified/Anon | Uphold | Gemini | bitFlyer ---- | ---- | ---- | ---- Screen Shot 2022-09-09 at 4 13 16 PM | Screen Shot 2022-09-09 at 4 19 27 PM | Screen Shot 2022-09-09 at 4 25 33 PM | スクリーンショット 2022-09-09 16 38 29 Screen Shot 2022-09-09 at 4 13 33 PM | Screen Shot 2022-09-09 at 4 19 34 PM | Screen Shot 2022-09-09 at 4 25 40 PM | スクリーンショット 2022-09-09 16 38 39 Screen Shot 2022-09-09 at 4 13 44 PM | Screen Shot 2022-09-09 at 4 19 44 PM | Screen Shot 2022-09-09 at 4 25 49 PM | スクリーンショット 2022-09-09 16 38 48 Screen Shot 2022-09-09 at 4 13 55 PM | Screen Shot 2022-09-09 at 4 19 50 PM | Screen Shot 2022-09-09 at 4 25 57 PM | スクリーンショット 2022-09-09 16 38 55 Logs: ``` [ REQUEST ] > URL: https://api.rewards.bravesoftware.com/v1/parameters > Method: GET ......... [ RESPONSE - OnRequest ] > Url: https://api.rewards.bravesoftware.com/v1/parameters > Result: Success > HTTP Code: 200 > Body: {"payoutStatus":{"unverified":"complete","uphold":"processing","gemini":"off","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.373245,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} [9782:259:0909/161306.952509:VERBOSE9:logging_util.cc(138)] [ RESPONSE HEADERS ] > Url: https://api.rewards.bravesoftware.com/v1/parameters ```
Uni-verse commented 2 years ago

Verification completed on Samsung GS 21 on Android 12 using the following build(s):

1.43.86 Chromium: 105.0.5195.68 (Official Build) (64-bit) 
Revision    ad13e82529051bac6a0e65f455e6d7a1e5fd7938-refs/branch-heads/5195@{#903}
OS  Android 12; Build/SP1A.210812.016

Testing based on https://github.com/brave/brave-browser/issues/24980#issuecomment-1231605389

1. For the below cases, confirmed when "complete" is returned from payoutStatus API, and it is on or after the payout date (ex. 7th in my case), and ad tokens were cashed in for the previous month, the "Arrived" message shows as expected:

Unverified/Anon - PASSED When using an unverified/anon setup for rewards (no custodial provider): - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured `/parameters` API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured `payment processing` status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Logs: ``` 10-01 20:05:46.182 26044 26044 V chromium: > Result: Success 10-01 20:05:46.182 26044 26044 V chromium: > HTTP Code: 200 10-01 20:05:46.182 26044 26044 V chromium: > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.337382,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} 10-01 20:05:46.182 26044 26044 V chromium: 10-01 20:05:46.188 26044 26044 V chromium: [VERBOSE1:api_parameters.cc(90)] Params timer set for 11148 s ```
Gemini - PASSED - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured /parameters API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured payment processing status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Logs: ``` 10-01 20:37:52.420 19048 19048 V chromium: > Url: https://api.rewards.bravesoftware.com/v1/parameters 10-01 20:37:52.420 19048 19048 V chromium: > Result: Success 10-01 20:37:52.420 19048 19048 V chromium: > HTTP Code: 200 10-01 20:37:52.420 19048 19048 V chromium: > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.342049,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} ```
Uphold - PASSED - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured /parameters API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured payment processing status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Logs: ``` 09-07 19:11:06.485 15628 15628 V chromium: [ RESPONSE - OnRequest ] 09-07 19:11:06.485 15628 15628 V chromium: > Url: https://api.rewards.bravesoftware.com/v1/parameters 09-07 19:11:06.485 15628 15628 V chromium: > Result: Success 09-07 19:11:06.485 15628 15628 V chromium: > HTTP Code: 200 09-07 19:11:06.485 15628 15628 V chromium: > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.338686,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} ```
bitFlyer - PASSED - Ensured payout status is fetched correctly and ensured there is no crash in browser - Ensured /parameters API endpoint is returning success response code 200 for payout status and ensured there are no error logs - Ensured payment processing status is not triggered when payout status is set as "Complete" at the server side - Ensured the "Arrived" message is shown in all expected places - Ensured the "Arrived" message is shown based on payoutStatus returned from API (I did not need to send myself an Ad grant to get this message to show) Logs: ``` 10-07 10:09:19.373 29430 29430 V chromium: [ RESPONSE - OnRequest ] 10-07 10:09:19.373 29430 29430 V chromium: > Url: https://api.rewards.bravesoftware.com/v1/parameters 10-07 10:09:19.373 29430 29430 V chromium: > Result: Success 10-07 10:09:19.373 29430 29430 V chromium: > HTTP Code: 200 10-07 10:09:19.373 29430 29430 V chromium: > Body: {"payoutStatus":{"unverified":"complete","uphold":"complete","gemini":"complete","bitflyer":"complete"},"custodianRegions":{"uphold":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"gemini":{"allow":["AU","AT","BE","CA","CO","DK","FI","HK","IE","IT","NL","NO","PT","SG","ES","SE","GB","US"],"block":[]},"bitflyer":{"allow":["JP"],"block":[]}},"batRate":0.341287,"autocontribute":{"choices":[1,2,3,5,7,10,20],"defaultChoice":1},"tips":{"defaultTipChoices":[1.25,5,10.5],"defaultMonthlyChoices":[1.25,5,10.5]}} ```
Arrived Rewards (Gemini/Uphold/Anon) Countdown message (Gemini/Uphold/Anon) bitFlyer Arrival bitFlyer Countdown message
screenshot-1661968815389 screenshot-1661980225391 screenshot-1661980300542 screenshot-1661982426781 screenshot-1661982473979