Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

LaunchData Broken on Android

Open
  • Is something wrong?
#65 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, firebase, javascript
Domain
mobile-dev

Research direction

The issue identifies the firebase.Messaging.launchData entry point and the notification-tap startup path; begin by reproducing the Android behavior on the listed devices and tracing how launch data is assigned. Compare the Android result with the provided iPhone output; done means launchData is populated after an Android notification tap with the custom data available to the app.

Written by the indexing model from the issue text.

Description

Problem description

LaunchData isn't set on Android upon launching the app through a notification.

Here is the console output after being launched with a notification tap on Android:

> Firebase token: <token>
> No launch data received.
Expected behavior

Here is the console output after being launched with a notification tap on iPhone:

> Firebase token: <token>
Custom Launch Data Detected:  { aps:
  { alert:
     { title: <title>,
       body: <body> } },
 'gcm.notification.data': '{<myCustomData>}',
 'google.c.a.e': '1',
 optinaldata1: 'value',
 'gcm.message_id': <id> }
Environment
  • Tabris.js version: 3.0.0-beta2-dev.20190306
  • Devices tested:
    • iPhone 7 with iOS 11.1.1
    • HTC Desire 530 with Android 6.0.1
    • Pixel 3XL with Android 9
Code snippet
/* ask for permissions */
if (device.platform == 'iOS') firebase.Messaging.requestPermissions();

console.log("Firebase token: " + firebase.Messaging.token);

setTimeout(() => { // workaround for Issue #41
	if (typeof firebase !== "undefined") {
		if (typeof firebase.Messaging.launchData !== "undefined" && firebase.Messaging.launchData) {
			console.log("Custom Launch Data Detected: ", firebase.Messaging.launchData);
		}
		else {
			console.log("No launch data received.");
		}
	}
});

Workaround for #41

Dominant language
JavaScript
Stars
6
Forks
5
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipsesource/tabris-plugin-firebase

All issues in eclipsesource/tabris-plugin-firebase

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.