-
Notifications
You must be signed in to change notification settings - Fork 180
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
Release latest #70
Comments
Looking forward to these updates. |
Shall we make v1.3.4 contain those fixes which can be done/merged relatively quickly, and leave the stuff which require more time to v1.4.0? In fact depending on the list of changes to be done, I think it may be better for the upcoming to be v1.4.0 followed by v1.5.0. |
I propose to include these in the upcoming release:
@dcousens @uniphonic what do you think? |
@tjwoon indeed, most of the above should be fixed, I just haven't had time to take it to a number of devices and thoroughly test yet. |
@tjwoon Sounds good to me, except I think maybe we should leave out #49. I think all of those have code fixes that have already been committed, with the exception of #49, which I was not able to reproduce. Everything else is already in master, correct? I think we should go ahead and release what we've got in master right now. I just tested it out the latest from master on a Samsung Galaxy S4, Nexus 5x, iPhone 6, and iPhone 4s, and it seems to be working fine for me. I had done more extensive testing on PR #65 , and didn't see any problems there either. |
Wow, progress spends awesome! I'll test #49 on some of my devices |
For me, I have to release this and do a production testing set within the next month (or so). |
Related #92 |
Related #87 |
edit: We really need to get the update out ASAP, as iOS crashes otherwise
The text was updated successfully, but these errors were encountered: