Contact birthday shortcut doesn't open calendar page

Bug Reports
,
1

REPRODUCIBILITY: 100% (always)
OSVERSION: 4.5.0.16
HARDWARE: Sony Xperia 10 III - xqbt52 - xqbt52 - 1.0.1.12 - aarch64
UI LANGUAGE: English (UK) (user: en_GB, os: en_GB.utf8)
REGRESSION: yes (since: 3.2 - arm)

DESCRIPTION:

Clicking on contact birthday doesn’t open the day in calendar.
Instead it opens the calendar with “Could not load page”.
The contact birthday is registered in the birthdays calendar.

PRECONDITIONS:

Contact has birthday filled.
Birthday is properly registered in calendar.

STEPS TO REPRODUCE:

  1. Open a contact with birthday filled
  2. Click on the calendar icon in contact details (next to the birthday )

EXPECTED RESULTS:

Calendar opens with birthday page loaded

ACTUAL RESULTS:

Calendar opens with “Could not load page”

MODIFICATIONS:

  • Patchmanager: no
  • OpenRepos: yes
  • Chum: yes
  • Other: none specified

ADDITIONAL INFORMATION:

Device Owner User: defaultuser
Home Encryption: enabled

the initial version of this bug report was created using Bugger 0.9.9+git1
2 
> lut 04 11:13:01 Sailfish dbus-daemon[5320]: dbus-daemon[5320]: [session uid=100000 pid=5320] Successfully activated service 'com.jolla.calendar.ui'
> lut 04 11:13:02 Sailfish jolla-calendar[8145]: [W] unknown:1283 - file:///usr/lib/qt5/qml/Sailfish/Silica/PageStack.qml:1283:13: QML AnimatedLoader: (file:///usr/share/jolla-calendar/pages/DayPage.qml: File not found)

@dcaliste Isn’t that because of your calendar changes?

1 Like
3

You can change line 40 in dbusinvoker.qml of jolla-calendar to:
pageStack.push("pages/AgendaPage.qml…
(from pages/DayPage) and it works opening the agenda of that day, but DayPage.qml is also mentioned in that agendapage so maybe actual daypage.qml did go missing, weird

4

Oups, yeh, I think you’re right. I’ll give a look. Thanks for pinging me.

1 Like
5

Ok, a fix is under review. Sorry, I was in vacation last week and was not able to work on it, so it missed the window before public release…

1 Like
6

Added to internal bugzilla

1 Like
7

From what I gather from your comment and our internal bugzilla, the fix should be in next public release, i.e. 4.6.0

1 Like