Bug #22283

[PROD][Android] Version 1.0.43 Does Not Go Into Log Crashlytic

Added by yap chekying 21 days ago. Updated about 4 hours ago.

Status:Pending PRODStart date:18 July 2025
Priority:HighDue date:
Assignee:yap chekying% Done:

100%

Category:-Spent time:-
Target version:-

Description

Update the app_id to match the one used in Firebase.

RE OCBC Business Mobile app Audit Findings - July 2025.msg (364 KB) yap chekying, 06 August 2025 11:12 AM

History

#1 Updated by yap chekying 21 days ago

  • Assignee changed from yap chekying to Hao Ter Tai

#2 Updated by yap chekying 21 days ago

  • Priority changed from Normal to High

#3 Updated by Hao Ter Tai 16 days ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

237981

22/7/2025 update google-service.json for uat and prod for crashlytic fixes

root cause: google-service.json file data not correct.

solution: separate and update UAT and PROD environment's google-service.json so that UAT crashes will enter UAT crashlytic while PROD crash will enter PROD crashlytic.

#4 Updated by Hao Ter Tai 16 days ago

  • Status changed from Resolved to Assigned
  • Assignee changed from Hao Ter Tai to yap chekying

#5 Updated by Hao Ter Tai 4 days ago

238,095
4/8/2025 [PROD][Android] Version 1.0.43 Does Not Go Into Log Crashlytic

update google-service.json for uat and prod to use the same crashlytic because if separate uat and prod, it is required to change app id.

#6 Updated by yap chekying 2 days ago

#7 Updated by yap chekying about 4 hours ago

  • Status changed from Pending UAT to Pending PROD

Also available in: Atom PDF