Opened on 07/28/2015 at 11:31:37 AM
Closed on 01/07/2016 at 02:30:28 PM
#2828 closed defect (fixed)
[Adblock Browser for iOS] [Settings] [Ad blocking] Filter lists don't display on screen
Reported by: | passbrains | Assignee: | |
---|---|---|---|
Priority: | P3 | Milestone: | Adblock-Browser-for-iOS-1.2.0 |
Module: | Adblock-Browser-for-iOS | Keywords: | salsita, v |
Cc: | jand, pavelz, vojtab, mario | Blocked By: | |
Blocking: | Platform: | Adblock Browser for iOS | |
Ready: | yes | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description (last modified by Shikitita)
Adapted from https://www.passbrains.com/dashboard/view-ticket.php?ticket_no=AKI-29
Environment
Apple + iPhone 4S + iOS 8.4
How to reproduce
- Run the app
- Go to settings
- Select Adblock Plus
- Select Ad blocking
(Two screen shots are shown for timings and the screen hasn't loaded)
Observed behaviour
The filter lists don't load in most cases.
Expected behaviour
Language specific filter lists should be displayed on the screen.
Attachments (2)
Change History (10)
Changed on 07/28/2015 at 11:31:49 AM by passbrains
Changed on 07/28/2015 at 11:31:50 AM by passbrains
comment:1 Changed on 07/28/2015 at 11:43:44 AM by Shikitita
- Description modified (diff)
- Summary changed from Adblock Plus screen does'nt load on most cases to [Adblock Browser for iOS] [Settings] [Ad blocking] Filter lists don't display on screen
comment:3 Changed on 09/07/2015 at 09:10:59 AM by philll
comment:4 Changed on 09/08/2015 at 08:37:50 AM by philll
- Sensitive unset
comment:5 Changed on 10/06/2015 at 08:01:36 AM by mario
- Cc mario added
- Component changed from Unknown to Adblock-Browser-for-iOS
comment:6 Changed on 10/12/2015 at 11:16:36 AM by mario
- Keywords salsita added
comment:7 Changed on 11/24/2015 at 01:03:22 PM by pavelz
- Keywords v added
comment:8 Changed on 01/07/2016 at 02:30:28 PM by mario
- Milestone set to Adblock-Browser-for-iOS-1.2.0
- Priority changed from Unknown to P3
- Ready set
- Resolution set to fixed
- Status changed from new to closed
We weren't able to reproduce this issue reliably. However it "should" be solved due to refactoring of corresponding components.
Please keep this in mind during the next QA iteration and re-open this issue if necessary.
The refactoring happened for 1.2.0 which is why I'll assign them to that milestone even though it has been closed already.
@Shikitia: Is this anyhow reliably reproducible for you?