Bug #22106
[UAT][Android][Telegraphic Transfer][Special Deal] App Crash When Open Terms & Conditions
| Status: | Closed | Start date: | 17 April 2025 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | yap chekying | % Done: | 0% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Steps to reproduce:
1. Select “Transactions” in side menu.
2. Select “Fund Transfer”.
3. Select “Telegraphic Transfer”.
4. Select "Source of Fund" - foreign currency account.
5. Select "Destination Account" - Tap on "Transfer to a new beneficiary" > Input SWIFT Code: CHASCATTCTS.
6. At SWIFT Code confirmation page, tap on "CONFIRM" button.
7. At New Beneficiary screen, input "Account Number: 131425", "Currency: USD", "Beneficiary Name", "Beneficiary Address", "Beneficiary Nickname" and tap on “CONTINUE” button.
7. At Telegraphic Transfer screen tap on “CONTINUE” button.
8. At Regulatory Information screen, input "Payment Purpose: 2015 - BUNKERS & STORES", "Resident Status: Resident", "Beneficiary Country of Residence: CANADA", "Beneficiary Category: A0-PERORANGAN", "Remitter Country of Residence: ID - RESIDEN", "Remitter Category: E0 - PERUSAHAAN", "Beneficiary Affiliation Status: N - BUKAN AFILIASI" and tap on "CONTINUE" button.
8. At Destination page, input "Contract No.: 8850421917697", "Dealer Name", and "Dealer Rate: 1.3282".
9. Under TRANSFER INFORMATION, input "Currency: USD", "Amount: 150", "Swift Charges Method: Ourselves" and tap on "CONTINUE" button.
10. At Notification screen, tap on "CONTINUE" button.
11. At Confirmation screen, tap on "Terms and Conditions".
Actual Result:
1. Android 15: after click "Terms and Conditions" the app is crash. (UAT tester test result)
2. Android 13: after click "Terms and Conditions" the app show error_wss01. (UAT tester test result)
3. CY test result (Android 10 with latest package: https://i.diawi.com/x4LRKq): After tap on "CONTINUE" button at Notification screen, hit error ERROR.MCB.9999999 ERROR.MCB.9999999
Expected Result:
Should not show error or crash.
Please refer to attached videos and screenshot.
History
#1 Updated by yap chekying 3 months ago
Note: You may use Contract No.: 0180021917720, one number can only use for one transaction.
#2 Updated by yap chekying 3 months ago
- Subject changed from [Android] [Telegraphic Transfer] App Crash When Open Terms & Conditions to [UAT][Android][Telegraphic Transfer] App Crash When Open Terms & Conditions
#3 Updated by yap chekying 3 months ago
- Subject changed from [UAT][Android][Telegraphic Transfer] App Crash When Open Terms & Conditions to [UAT][Android][Telegraphic Transfer][Special Deal] App Crash When Open Terms & Conditions
#4 Updated by yap chekying 2 months ago
- File WhatsApp Video 2025-05-20 at 14.32.54.mp4 added
- Status changed from New to Pending PROD
- Assignee changed from sengloong.khoo sengloong.khoo to yap chekying
#5 Updated by yap chekying about 2 months ago
- Status changed from Pending PROD to Closed
#6 Updated by yap chekying 6 days ago
- Status changed from Closed to Assigned
- Assignee changed from yap chekying to sengloong.khoo sengloong.khoo
please help to provide root cause and solution
#7 Updated by sengloong.khoo sengloong.khoo 5 days ago
- Assignee changed from sengloong.khoo sengloong.khoo to yap chekying
Refer 22101 as due to changing calling getsTransactionFundTransferStep1 FE require to call additional transactionBeneficiaryInquiry due to the BE return different type of t&c pdf without calling Inquiry BE didn't know is for TT Transfer so t&c isreturn null
#8 Updated by yap chekying 5 days ago
- Assignee changed from yap chekying to sengloong.khoo sengloong.khoo
the root cause provided is unclear, and the solution is missing.
#9 Updated by sengloong.khoo sengloong.khoo 5 days ago
- Assignee changed from sengloong.khoo sengloong.khoo to yap chekying
Root Cause:
The application crash occurred during the Telegraphic Transfer (TT) flow in the Business-As-Usual (BAU) process. Specifically, the Android frontend (FE) is calling the getsTransactionFundTransferStep1 web service directly without retrieving the necessary Terms and Conditions (T&C) value beforehand.
Since the backend (BE) does not return the T&C value for TT in this call alone, this leads to a null value being passed when the user ticks the confirmation checkbox. As a result, the app encounters a null pointer exception and crashes.
Solution:
To resolve this issue, the Android frontend needs to make an additional web service call to transactionBeneficiaryInquiry before calling getsTransactionFundTransferStep1.
The transactionBeneficiaryInquiry service provides the required T&C value.
The getsTransactionFundTransferStep1 continues to provide the transactionPurposeList.
By calling both services, the frontend will be able to retrieve all necessary data:
The T&C value (used for confirmation),
The Transaction Purpose List (used in dropdown selections or form validations).
This ensures that both values are not null and prevents the app from crashing when the user proceeds with the TT confirmation.
#10 Updated by yap chekying 5 days ago
- Status changed from Assigned to Closed