/data/user/0/com.google.android.apps.messaging/files/httpft_pending (No such file or directory)

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:

• For general technical questions, post a question on StackOverflow with the firebase tag.
• For general Firebase discussion, use the firebase-talk google group.
• For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 3.6.2
• Google services: 4.3.3
• AGP: 3.6.3
• Firebase Components & Versions: firebase-core: 17.3.0 firebase-analytics:17.3.0 firebase-crashlytics:17.0.0-beta04 firebase-messaging:20.1.5

[REQUIRED] Step 3: Describe the problem

Hi - I ran into something interesting with this particular issue, and wondering if this might sound like a possible proguard issue that makes it not possible to detect certain models within Firebase?

I am able to receive push notifications from a server that is hooked into our Firebase console in debug, but not in release without setting debuggable to true.

I’ve also validated that I am indeed successfully generating an Firebase instance id and having that token registered (see more below).

I’ve tried the following combinations:

Does not work

 release {
            minifyEnabled true
            shrinkResources true
            signingConfig signingConfigs.release
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
            ...
        }

Does work

 release {
            debuggable true
            minifyEnabled true
            shrinkResources true
            signingConfig signingConfigs.release
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
            ...
        }

Does not work

 release {
            minifyEnabled false
            shrinkResources false
            signingConfig signingConfigs.release
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
            ...
        }

Does work

 release {
            debuggable true
            minifyEnabled false
            shrinkResources false
            signingConfig signingConfigs.release
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
            ...
        }

As a sanity check, I’ve downloaded the latest version of google.services from our console, and I’ve also tried experimenting with different versions for firebase, and AGP.

I printed out some Toasts/Alerts/Notifications to confirm that the release is in fact, generating a Firebase instance id and registering the new token.

Before	After

However, nothing occurs for onMessageReceived.

Steps to reproduce:

One could follow the steps to produce any UI components printing out subscriptions, generated Id’s etc. when accessing Firebase instances for generating ids, subscribing to topics.

I am able to successfully receive a notification message from the console itself on release (no debuggable). But still not the push notifications from the Heroku web app we’ve hooked into our console.

Relevant Code:

Added the following to see if I would be able to detect anything here:

override fun onMessageReceived(remoteMessage: RemoteMessage) {
        showNotification("", "Notification received", "$remoteMessage")
        val notification = remoteMessage.notification
        val topic = if (remoteMessage.data.isEmpty()) { 
            remoteMessage.from?.let { getConferenceId(it) } ?: ""
        } else {
            remoteMessage.data[EXTRA_CONFERENCE_ID] ?: ""
        }
        logger.log(TAG, "Received push notification from topic $topic: ${notification?.title} |  ${notification?.body}")

        showNotification(topic, notification?.title ?: "", notification?.body ?: "")
    }

Where showNotification creates a notification, but we never actually hit that point in here. I know that release is successful in calling onNewToken:

 override fun onNewToken(token: String) {
        super.onNewToken(token)
        logger.log(TAG, "Token received.")
        showNotification("", "Token received", "Received")
    }

[google-oss-bot]

Since there haven’t been any recent updates here, I am going to close this issue.

@ahinchman1 if you’re still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

[google-oss-bot]

Hey @ahinchman1. We need more information to resolve this issue but there hasn’t been an update in 5 weekdays. I’m marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!