Skip to content
This repository has been archived by the owner on Jun 7, 2020. It is now read-only.

[BUG] No Failure Message if Send of an Image failed #537

Closed
bochos-bln opened this issue Jul 19, 2017 · 4 comments
Closed

[BUG] No Failure Message if Send of an Image failed #537

bochos-bln opened this issue Jul 19, 2017 · 4 comments

Comments

@bochos-bln
Copy link

bochos-bln commented Jul 19, 2017

Users reported the following Issue with the Chat, during bad Network e.g. in Subway.

Steps to Reproduce from everywhere (not only in Subway):

  1. Action: Start a Chat

  2. Action: Turn Off Internet

  3. Action: Add a Image to the Chat (Camera or Camera Roll)
    3.1 Result/Failure: Image did not appear in Chat
    3.2 Result/Failure: No Failure Message
    3.3 Result Image not send
    3.4 Details: In SubscriptionManager the Completion Block is queued but callback is never called

  4. Action: Next, Turn On Internet (Do not touch Reconnect)

  5. Action Add a Image to the Chat (Camera or Camera Roll)
    5.1 Result/Failure: Image did not appear in Chat
    5.2 Result/Failure: No Failure Message
    5.3 Result: Image not send

  6. Action: Touch Reconnect

  7. Action: Writing now something, sending Image
    7.1 Result/Success: Message/Image Appears in Chat
    7.2 Image send

Using the Developer Option in iOS Setting (https://stackoverflow.com/a/40132545), enable Network Link Conditioner to 100% Loss also Text Messages are not send and the Send Button is enabled. This Text Messages seam to be never send. Don't matter the perfect Internet Connection Later or leaving, re enter the same Chat the still appear in unsend gray.

@rafaelks
Copy link
Contributor

@xlbs-rm Thanks for opening the issue and writing down all the steps. The networking sync is something we need to still work on to fix this bad paths. I'll let this issue opened.

@rafaelks rafaelks changed the title No Failure Message if Send of an Image failed [BUG] No Failure Message if Send of an Image failed Oct 5, 2017
@rafaelks rafaelks added this to the 1.7.3 milestone Nov 9, 2017
@rafaelks
Copy link
Contributor

rafaelks commented Nov 9, 2017

This one should be fixed with #830.

@cardoso cardoso removed this from the 1.7.3 milestone Nov 17, 2017
@rafaelks rafaelks added this to the 1.8.0 milestone Dec 7, 2017
@rafaelks rafaelks removed this from the 1.8.0 milestone Jan 2, 2018
@cardoso
Copy link
Collaborator

cardoso commented Jan 5, 2018

Should we close this @rafaelks ?

@rafaelks
Copy link
Contributor

rafaelks commented Jan 5, 2018

@cardoso Yes!

@rafaelks rafaelks closed this as completed Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants