co-epi / app-ios Goto Github PK

When I open Build 86 and go to Contact Alerts, it displays “Updating…” for awhile (maybe 30-60s) and then displays "Error updating: error(message: "Couldn't parse response: ke" (with the rest of the message cut off and not scrollable).

I'm creating this issue so it can be assigned to myself. Sorry if this is not the place ;)

Description
Many of the UI elements are broken if the device is turned to landscape. See screenshots below:

To Reproduce
In simulator:

• In menu bar select Hardware > Rotate Left/Right

On hardware:

• Turn off rotation lock in control center

• Rotate iPhone

Resolution
I see no reason that we can not simply disable Landscape mode all together. This is done here by unchecking the landscape boxes:

Currently, exposure matches are displayed in UTC. It'd be more convenient if they used the local system timezone instead.

Describe the bug
When building on the iPhone SE in the simulator, the symptoms label does not fit on the screen.

To Reproduce
Steps to reproduce the behavior:

1. Download the iOS 12.4 simulator under Xcode > Preferences > Components > iOS 12.4 Simulator
2. Select iPhone SE or iPhone 5s under the simulator selection menu
3. Build and Run

Expected behavior
Either a fixed smaller size for the label that works for all phone sizes or a dynamically resizing label.

Screenshots

Please link 'how is my data used' on onboarding screen to https://www.coepi.org/privacy/ for now

Problem: With turbulent changes in this rep, it's unclear for new users/testers how to build the app and which branch to use.

Solution* Add two entries to the README for this repo:

• A pointer to "Getting Started" a build instructions doc (and might as well add testing instructions, too). (Mark Ingle has written a build doc for iOS already).
• A (dynamically changing?) note in the README abut which repo branch to build from.

After hitting 'acknowledge', the contact alert page shouldn't re-show the same alerts over and over again.

I think I'm not alone in finding that the project.pbxproj causes issues when merging.

Does anybody have any experience with:

https://github.com/truebit/xUnique

It may take some of the headache away from merging. (Or maybe its just me!)

Once Co-Epi/coepi-backend-aws#6 is complete, transition the app to use it.

When trying building develop, I get the following error:

Describe the bug
When clicking to open the debug menu, the app crashes. The breakpoint is shown below.

Apple says:

We identified one or more issues with a recent delivery for your app, "CoEpi.org" 0.1 (1). Your delivery was successful, but you may wish to correct the following issues in your next delivery:

ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of new apps that use UIWebView APIs starting from April 2020. See https://developer.apple.com/documentation/uikit/uiwebview for more information.

Home screen with navigation bar and 2 tappable cards

Build on previous internationalization work (English/Spanish) to translate CoEpi into 8 other languages: German, French, Portuguese, Chinese (traditional/simplified), Korean, Russian, and Japanese.

Onboarding screen uses HTML rendering for 3 labels shown. This seems to impact the duration of the app startup.
Set labels to use Roboto fonts as in design.

We should display the version number, build number, and/or git commit on the home or debug screen so we can be sure which version someone is running when testing.

Problem.
If you did not know that the symptoms were a scrolling list, all but the 8 Plus give no indication that there is more to the list. See the picture below:

Describe the solution
A solution would be to flash the scroll bar when the page loads to show users that it is not a static list (https://developer.apple.com/documentation/uikit/uiscrollview/1619435-flashscrollindicators).

Alternatives
A suitable alternative would be to remove the scrolling all together in favor of a static list that we test on each device.

Describe the bug
Submit button for symptoms reports even if nothing is selected - should be disabled unless a box has been ticked

Describe the bug
The app starts up then crashes...See screenshot of dump

To Reproduce
Steps to reproduce the behavior:
Connect phone via USB, then click on run arrow

Expected behavior
App should run on iPhone

Screenshots

Once users select symptoms, prompt them to pick a date when each of the selected symptoms started.

Black on dark blue is really hard to read.

Hi,

I want to ask if is possible to scan devices around, including Android, and detect, without connecting, those peripherals and after detecting, just exchange data.

I want to build an app that wakes up just to scan e exchange data, without connecting both.

I tested your app and i saw that, the scan works only if the service UUID is unique, and you force the scan search for that same one, correct?

Thank you,
Rhullian Damião

A few duplicate files in the "compile sources build phase"

Place the number of unacknowledged exposure matches as a red badge on the app icon.

CoEpi build 70 has used 55% of my battery over the last day from background activity, draining the phone's battery over the course of a few hours.

We need to make sure we're only processing each TCN Key a single time (the first time we download it). If that doesn't account for the vast majority of the background energy usage, we might need to profile what else is being performed continually in the background.

See Figma for details.

Note - may tweak the background rectangle 'texture' design, so can be built in the interim to focus on buttons etc.

iOS <-> Backend communication using RxAlamofire

iOS app currently does not have a Launch Screen. An empty white screen is shown instead (when starting the app).
Add custom Launch screen.
https://www.iosapptemplates.com/blog/ios-programming/ios-launch-screen

Allow to update alerts manually and show a label when an update is happening. For now aimed to testers. Unclear whether it should be available for regular users.

If the app detects an exposure match in the background, issue a notification.

Separate responsibilities. Data base related in Realm... repo. Pure business logic (generateCENData in this case) here.

Originally posted by @i-schuetz in #25

#25 (comment)
#25 (comment)
#25 (comment)

Share functionality does work on iOS 12 from the home screen (tap share; choose to text to someone, etc. works).

However, now after entering symptoms on iOS 12 with build62, the share notification pops up. Choosing either option (don't share or share) results in the same behavior: staying on the symptom screen. Symptoms do not appear to be submitted.

Overall, I would recommend removing share functionality from the symptom entering workflow, and leave it only as a home page option. We shouldn't prompt someone to share the app with a basic app behavior of entering symptoms.

Currently there can be a transition to the next rounded timestamp in the delay between the CEN generation by the sender and the storing by the receiver (which sets its timestamp to "now").

With the current algorithm, this should be fixed by generating a candidate CEN for the previous rounded time stamp too.

Prepare for translation to other languages, starting with Spanish as an example.

https://developer.apple.com/internationalization/

https://fonts.google.com/specimen/Roboto?selection.family=Roboto

CEN matching logic should be easy to paralelise and run on multiple cores (num cores = 4?) . This should yield linear performance gains.
Currently, logic is single threaded.

(see Android implementation)

Should be reusable, integrated with Rx.
Currently displayed during fetching alerts (matching) and submitting a report.

See Figma for details.

When I load the debug screen on an iPhone 6s running iOS 12.4, there's no way to slide it down to get back to the home screen, and I have to kill the app to get out of the debug screen.

RxSwift / iOS platform bug:
RxSwiftCommunity/RxDataSources#331

Appears to cause only a warning.

Warning once only: UITableView was told to layout its visible cells and other contents without being in the view hierarchy (the table view or one of its superviews has not been added to a window). This may cause bugs by forcing views inside the table view to load and perform layout without accurate information (e.g. table view bounds, trait collection, layout margins, safe area insets, etc), and will also cause unnecessary performance overhead due to extra layout passes.

@johnsonh

Symptom list has two items below the fold only visible upon scroll. No scroll bar is visible and scroll has very low discoverability as the list appears complete.

Suggest adding a scroll bar or other visual indication of scroll to get to more features.

v0.1(66)
iOS 13.3.1, iPhone X

Implement share buttons in homepage and share popup after reporting first set of symptoms to encourage users to grow the user base

When displaying an exposure match, symptom information in the report should be displayed along with the time stamp of the match.

Before we add more changes to this screen, it should be refactored to show all the entries (including the debug data) in a table view. If needed, see debug view model for table view with mixed row types example.

When you have a list of new contact alerts, after tapping to select different alerts multiple times, eventually the text will become scrambled.

Screenshots

Hi Dana and Scott,

Hope you’re well.

I have a team of highly skilled developers in Native Mobile on iOS and Android, as well as Backend and System Architects waiting in the wings ready to build out a Contact Tracer system.

Do you have some time to talk today or tomorrow? I’m on PST. My email is Rnorback [@] gmail.com.

Best,
Rob Norback