Ask / Submit
9

Why does the Giggity android app trigger a Jolla browser start instead of displaying a schedule? [released]

asked 2013-12-29 17:10:55 +0300

t-lo gravatar image

Giggity is a FOSS Android app which displays schedules of various conferences. Giggity is available to Jolla users via the Android compatibility / F-Droid store.

Steps to reproduce - Start Giggity: a list of available schedules will pop up - Touch the entry "30C3"

Expected results - The schedule is displayed in the Giggity app.

Actual results - The Jolla native (!) browser opens an URL displaying the schedule XML.

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by nthn
close date 2014-12-21 01:39:32.199371

3 Answers

Sort by » oldest newest most voted
2

answered 2014-12-21 00:53:00 +0300

raimue gravatar image

As of update10 (1.1.1.27 Vaarainjärvi) this works correctly for me with Giggity and also with Öffi. I cannot confirm whether this was already fixed in the opt-in-only update9 as I did not have it installed.

edit flag offensive delete publish link more

Comments

I can confirm that also RedReader (which suffered from the same problem) now works.

magullo ( 2014-12-22 12:45:02 +0300 )edit
1

answered 2013-12-29 17:32:04 +0300

Bulder gravatar image

This is because some apps like to install additional stuff that is then defaulted to themselves. For example, Google Drive cannot open drive files in the app, but opens them in the browser. Were this default Android, the OS would catch the (for example) 'giggity://' link it uses for the command to the other module. Unfortunately SailfishOS doesn't catch them into the Alien-Dalvik, and instead handles them in the browser.

edit flag offensive delete publish link more

Comments

1

I don't think that's the whole story - I guess that giggity merely tries to open a HTTP URL. Sailfish OS (or Alien Dalvik) should not interfere here since interfering will break other Android apps' workflows, too.

t-lo ( 2013-12-29 18:29:19 +0300 )edit
1

answered 2014-01-28 12:01:02 +0300

Dekkers gravatar image

I just talked to Wilmer, the developer of giggity. What giggity does is the following:

Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(url),
                           this, ScheduleViewActivity.class);
intent.putExtra("PREFER_CACHED", !prefOnline);
if (sel != null)
    intent.putExtra("SELECTIONS", sel);
startActivity(intent);

It explicitely says the intent should be handled by the ScheduleViewActivity class, but somehow Alien Dalvik ends up opening the browser instead of the ScheduleViewActivity class. It looks like a bug in Alien Dalvik, but I currently don't have the time to investigate it further.

edit flag offensive delete publish link more

Comments

I see the exact same behaviour in Öffi, a german public transport app that opens connections as xml in the sailfish browser.

Another annoying thing is apps opening oauth links with sailfish browser resulting in a broken oauth experience. I guess this doesn't belong here though.

MoritzJT ( 2014-02-03 00:16:28 +0300 )edit

It is very annoying that one of the most popular apps in Germany Öffi is still not working with the latest update (1.0.7.16).

birefringence ( 2014-06-22 21:52:24 +0300 )edit

Question tools

Follow
4 followers

Stats

Asked: 2013-12-29 17:10:55 +0300

Seen: 379 times

Last updated: Dec 21 '14