githubbob42 / mingle2github2

0 stars 1 forks source link

iOS detail pages not loading on refresh of browser #5484

Open githubbob42 opened 5 years ago

githubbob42 commented 5 years ago

Mingle Card: 5845 This is simply a fact of how a single page app works. The user must go back to the “entry point”. In this case, they need to go back to their bookmark which is www.fieldfx.com

YM – now that we only support running fieldfx in the native browser on iOS 11 (and not the webclip) this will potentially become more problematic. We can fix this by changing routing to use hashes instead of paths so the app can reload from any url

Steps to Reproduce

| | |
|-|-|
|**Version #**|4.0.1.4052|
|**Hardware**|iPad|
|**OS**|iOS 11.3|
|**Browser**|Safari|
|**Username**|lfwtest@mailinator.com|
|**Password**|Use LastPass|
|ORG ID|00D41000001Mhom|
|User ID|005410000056nHq|
|RayGun Error ID| |
  1. log into mobile app
  2. disconnect network connection
  3. click on any Job Detail or Ticket Detail or checklist or Ticket Item list
  4. Refresh the page

Expected Result

when offline, the mobile app should refresh the page successfully and save any changes you have made.

Actual Result

When trying to refresh a page in the mobile app, while offline, Safari does not reload the page and generates an error msg “Safari cannot open the page “https://fieldfx.com/…...” because your iPad is not connected to the Internet.

Analysis

Related Cards

Steps for Creating a Defect Card

| | |
|-|-|

1

   |

Ensure the defect title and description is clear and understandable.

   |

   |

2.

   |

Ensure the following are listed on the card:

    *   Mobile or back office version.
    *   Operating system
    *   Devices
    *   Browsers
    *   Username/Password.

   |

   |

3. 

   |

Ensure there are steps to reproduce and are easy to follow.

Add screenshots as necessary for clarity

   |

   |

4. 

   |

Ensure the Expected and Actual results are listed.

   |

   |

5.

   |

Check whether the bug exists in production (Sync V4) and/or Sync V4 Beta

    *   If the bug exists in current production then select the “**Sync V4 Channel”**
    *   If the bug exists in the Beta Channel but is not in production yet, then select “**Beta Channel”**
    *   If the bug was created during current iteration then select "**Regression**”

   |

   |

Test Plan

| | |
|-|-|

1.

   |

Ensure the card has enough information from the programmer before you start the verification

If not request more information

   |

   |

2.

   |

Ensure you’re able to reproduce the defect prior to verifying it

   |

   |

3.

   |

Ensure to verify if the PR is still valid by going to Github.

   |

   |

3.

   |

Create a test plan and write/update test case for the card is there is no test case in Tarantula.

   |

   |

4

   |

Test the card on all required devices and versions. If it’s a mobile card, always test the offline functionality around that defect. Attach screenshots to the card as necessary displaying the fix

   |

   |

5.

   |

Add the following test result documentations:

    *   Test Status:
    *   PR Build:
    *   Username/Password
    *   Test case name:
    *   Environment and devices tested on:
    *   Test Note.

   |

   |

6.

   |

Push the card to “Testing Complete”

   |

   |