Issue | Impact | Solution | Platform | Owner |
|---|---|---|---|---|
Push notification DOESN´T works on Android version higher than 12 | Android greater than 12 | Capacitor upgrade | Android | RBI |
Push notification DOESN´T trigger when the application is closed | Android application is CLOSED | Sales force send the notification object on the payload | Android | Salesforce |
IOS devices are not being opted-in | DON´T work on iOS application | Change swizziling configuration on the firebase | iOS | Dedicated team |
Change push notification arch using mParticle to integrate with Salesforce | Architeture improvement | Change architecture on push solution using mParticle | Android - iOS | Dedicated team(TO PRIORITIZE) |
Issue | Platform | Salesforce Ticket | Jira Ticket | Team | Status |
|---|---|---|---|---|---|
Push notification DOESN´T works on Android version higher than 12 | Android | N/A | ???? | Jun 06th - Prioritizing between RBI teams, currently, we don´t know will ownership itTO PRIORITIZE | |
Push notification DOESN´T trigger when the application is closed | Android - iOS | #44660988 | Salesforce | Jun 06th - Salesforce team is analysing to add notification on the body payload Jun 07th - Iberia and SalesForce had a meeting to have a duedate from salesforce request Jun 12 - The SalesForce team has responded to our request, suggesting the use of the REST API to send push notifications to the application.While we acknowledge their suggestion, we have concerns about whether this is the most suitable approach for sending push notifications. It is possible that gonna sends the push notification needs the developer skills to handle it.Rapha has requested the REST API for evaluation purposes, but based on our assessment, it does not appear to be the optimal solution. | |
IOS devices are not being opted-in | iOS | #44681335 | Dedicated team | Jun 06th - Based on Salesforce suggestion, the Dedicated team will change a configuration on Firebase and test if it gonna work well IN PROGRESS Jun 07th - The dedicated team diligently applied the recommended configurations to prevent iOS method swizzling, as advised by Salesforce. Unfortunately, these measures did not yield the desired results, and we are currently engaged in the debugging process to ascertain what went wrong with the application. Jun 08th - Following the suggestion, we have added the "FirebaseAppDelegateProxyEnabled" boolean tag to the info.plist file. However, this implementation has resulted in an "device token: not yet set" error. After thorough debugging, we have determined that iOS is generating the token, but mcordova is not sending it to the Salesforce application. We are currently investigating this issue to identify the root cause and find a solution. Jun 12 - As mentioned in the previous status update, we have been encountering difficulties in receiving the token. Today, we diligently tested several potential solutions, but unfortunately, none of them have proven successful. After extensive research and reading through the documentation, we came across a thread indicating that the issue may be related to building the application using a development IDE(Xcode). Consequently, our current approach involves building the application on a physical device in order to thoroughly test it. Jun 13 - Today, we have completed all the configurations as instructed in the documentations. The good news is that we have resolved the "device token: not set yet" error.We were able to retrieve the token and verify it in the development tool logs. Yesterday we faced a problem regarding the user status("Not opted in") on the salesforce application, we have successfully changed the status from "Not opted In" to "Opted In.". However, despite these advancements, we are currently facing an issue where we are not receiving the push notifications.When testing with Postman, we received a response indicating an "invalid registration." Our next steps involve investigating the reason behind not being registered, as we are technically sending the token to Salesforce. | |
In-app message sent only to home screen | iOS | #44673376 | Dedicated team | Jun 06th - Salesforce suggested to add track method. The dedicated the IN PROGRESS Jun 07th - We have implemented the recommended method for in-app messaging, but initially encountered an issue with the message displaying an "invalid callback_id" error. After an extensive debugging session, we were able to identify and resolve the problem. Our next step is to apply the solution to a generic flow and test its effectiveness. Jun 13 - As agreed, we have prioritized the configuration and sending of in-app messages for the sign-up and sign-in flows.We are actively working on a solution to support in-app messages for page view flows. To simplify the process, we are developing a solution that eliminates the need for advanced development skills. This means that the designated owner or member responsible for sending the in-app messages will have the autonomy to do so independently. The ETA to have it implemented and ready to go to QA env in the end of this week(Jun 16th) | |
Change push notification arch using mParticle to integrate with Salesforce | Android - iOS | N/A | Dedicated team | Jun 06th - On Dedicated team backlog TO PRIORITIZE |
0 Comments