Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offline support #7

Open
zubozrout opened this issue Sep 3, 2015 · 8 comments
Open

Offline support #7

zubozrout opened this issue Sep 3, 2015 · 8 comments
Milestone

Comments

@zubozrout
Copy link

Hi,
Hangups are currently unusable offline and any attempt to send a message in such way ends up with an error. Usually this would not be an issue, but sometimes I can't get around such situation, especially in the underground (Prague), with mobile network signal only covering stations.

This is probably not the only issue with the app being offline. As far as I know we can't even start the app offline - a little caching could manage that - which would be great for example for accessing old messages even offline, or preparing a message to be sent later.

However, we all know Hangups is a work in progress and just begun its journey. This is just a suggestion which would severally improve the overall user experience. Also, Telegram on Ubuntu Phone is here for a long time now and can't manage this either ... messages sent offline with Telegram gets stuck and nothing can persuade them to be sent later on except copying, deleting and trying again.

Thank you

@zubozrout
Copy link
Author

Here is the message, parsed using OCR, but I think it is better than posting the screenshot of the dialogue itself:

An error has occured: Return value
of PyObject call is NULL: Traceback
(most recent call last):

File "/opt/click.ubuntu.com/
ubuntu-hangups.timsueberkrueb/
0.1.6/backend/_init_.py", line 410,
in set_typing
call_threadsaFe(conv_controllers[
conv_id].set_typing, typing);

File "/opt/click.ubuntu.com/
ubuntu-hangups.timsueberkrueb/
0.1.6/backend/_init_.py", line 440,
in call_threadsafe
loop.call_soon_threadsafe(callbac
k, *args)

File "/usr/lib/python3.4/asyncio/
base_events.py", line 462, in
call_soon_threadsafe
handle = self._call_soon(callback,
args)

File "/usr/lib/python3.4/asyncio/
base_events.py", line 436, in
_call_soon
self._check_closed()

File "/usr/lib/python3.4/asyncio/
base_events.py", line 265, in
_check_closed
raise RuntimeError(‘Event loop is
closed')

RuntimeError: Event loop is Closed

@StuntsPT
Copy link

I think this should be filed upstream, since it is also a problem in hangups itself.

@timsueberkrueb
Copy link
Owner

@StuntsPT Hmm, I think this should be handled app-side. If this problem also exists in the command line Hangups I think you can create a feature request there.

@tdryer
Copy link

tdryer commented Sep 16, 2015

Opened a hangups issue: tdryer/hangups#164.

@timsueberkrueb timsueberkrueb modified the milestone: v0.3 Oct 8, 2015
@timsueberkrueb
Copy link
Owner

I'll move this to v0.4. An maintenance update for the current store version is required (as e.g. image sending doesn't work any more in v0.2) and thus I'll release v0.3 soon. I'll implement this feature as soon as it's implemented upstream :)

@bittner
Copy link

bittner commented Sep 21, 2016

I'd like to move this feature onto the top of the list of the current milestone, haha! 😃 There's no voting on GitHub for an entire ticket, so ...

@tim-sueberkrueb Do you have any preference to change priorities now that OTA-13 is out?

@timsueberkrueb
Copy link
Owner

@bittner first priority is #66 right now :)

@StuntsPT
Copy link

StuntsPT commented Nov 4, 2016

There is a possible workaround for this issue:
tdryer/hangups#272
At the very least this should avoid the ugly error we get when off-line.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants