I believe I may have found the source of the problem. When the scope is aggregated, the author assumed they can access results[0], which may not be true if:
1) the user is signed in
2) but has no messages whatsoever
That'd mean the scope would crash for all users, who have set up Telegram account, but not really used it.
Michi, if you have time, perhaps you could verify my finding. In the mean time, I'm rewriting the scope source as the backing database schema has changed (after we moved to making use of TelegramQML plugin).
I believe I may have found the source of the problem. When the scope is aggregated, the author assumed they can access results[0], which may not be true if:
1) the user is signed in
2) but has no messages whatsoever
That'd mean the scope would crash for all users, who have set up Telegram account, but not really used it.
Michi, if you have time, perhaps you could verify my finding. In the mean time, I'm rewriting the scope source as the backing database schema has changed (after we moved to making use of TelegramQML plugin).