A user reported that SMS verification codes from GPSurgery / NHSNoReply were not appearing in Messaging and notifications only showed a generic Message.
The bugreport shows the SMS was delivered by telephony and handed to Messaging, but the app's receive action did not run until the user opened Messaging about 1 minute later. The first click on the notification didn't open the Messaging app.
From logs:
06-15 11:32:27.448: modem/IMS reports a new SMS06-15 11:32:27.601: sender GPSurgery checked and not blocked06-15 11:32:27.749: SmsReceiver.deliverSmsMessages06-15 11:32:27.760: ActionServiceImpl#1000 job is scheduled- No
ReceiveSmsMessageAction execution at that time
06-15 11:33:28.433: user opens Messaging06-15 11:33:28.866 through 11:33:29.746: queued SMS receive actions finally run and messages are imported- Notification update around this time is for an unrelated conversation, not the newly imported SMS conversations
This suggests the SMS delivery path reaches Messaging, but the legacy JobIntentService / ActionServiceImpl work can remain queued while the app is in the background.
SMS delivery reaches SmsReceiver.deliverSmsMessages, but ReceiveSmsMessageAction does not run until the app is opened later. During that window the message is not visible in the app and the notification is generic or missing useful content.
Suspected area: SmsDeliverReceiver / SmsReceiver.deliverSmsMessages() -> ReceiveSmsMessageAction.start() -> ActionServiceImpl.enqueueWork() / JobIntentService.
I wasn't able to reproduce it.
A user reported that SMS verification codes from
GPSurgery/NHSNoReplywere not appearing in Messaging and notifications only showed a genericMessage.The bugreport shows the SMS was delivered by telephony and handed to Messaging, but the app's receive action did not run until the user opened Messaging about 1 minute later. The first click on the notification didn't open the Messaging app.
From logs:
06-15 11:32:27.448: modem/IMS reports a new SMS06-15 11:32:27.601: senderGPSurgerychecked and not blocked06-15 11:32:27.749:SmsReceiver.deliverSmsMessages06-15 11:32:27.760:ActionServiceImpl#1000job is scheduledReceiveSmsMessageActionexecution at that time06-15 11:33:28.433: user opens Messaging06-15 11:33:28.866through11:33:29.746: queued SMS receive actions finally run and messages are importedThis suggests the SMS delivery path reaches Messaging, but the legacy
JobIntentService/ActionServiceImplwork can remain queued while the app is in the background.SMS delivery reaches
SmsReceiver.deliverSmsMessages, butReceiveSmsMessageActiondoes not run until the app is opened later. During that window the message is not visible in the app and the notification is generic or missing useful content.Suspected area:
SmsDeliverReceiver/SmsReceiver.deliverSmsMessages()->ReceiveSmsMessageAction.start()->ActionServiceImpl.enqueueWork()/JobIntentService.I wasn't able to reproduce it.