[robert65]

Hi Mobione team, while I await a solution on a previous post I wonder if you could answer the following points as I remain a bit puzzled with the release of 2.0

1) what was changed in M2 to M3 prior to 2.0 being accepted as the official release
2) What causes the pop up message that I posted in the M3 thread and now exists in 2.0 that did not exist in M2
3) have other users experienced the same issues as I don’t think that mine is an isolated incident
4) it is my opinion M2 was by far the best release to combine iOS and android as no errors appeared during the build and no frozen screen which I highlighted in my M3 thread and still exists in 2.0, do you have any positive reports in the short time of the release of 2.0 was a bit premature?
5) If the errors persist would there be anyway that M2 could be reviewed for release or would I need to look at the possibility of dumping android and going back to 1.5 version

[support-michael]

Hi Robert,

I want to personally thank you for the feedback across the 3 milestone versions. It was very helpful in improving the final 2.0 product. My understanding is you have only 1 outstanding issue report towards 2.0 production regarding your iOS app’s UI hanging up. We are researching it now and will provide feedback asap. You stated that you reported the hanging UI issue as part of milestone-3 (not 2.0 production). I was not aware of such a report otherwise it would have been investigated and feedback provided. We spent several days resolving specific issues you reported on M2 and M3.

Regarding 2.0 milestone-2 being a good release. I can assure if we felt that 2.0m2 was worthy of being promoted to the final 2.0 production release we would have done so. We would have been able to avoid the many late nights and long weekends between it and the actual production release. I reviewed the changes from m2 to 2.0 and there are at least 50 improvements and bug fixes.

What may be troubling you is that you have been party to the evolution of 2.0 across the 3 intermediate milestone versions. You have seen the reality of software evolving which means it breaks sometimes. This is a common challenge with milestone release programs and that is these are works-in-progress that continue to evolve. Sometimes the evolution may not be backward compatible… although if such cases arise we go way out of our way to avoid inconveniencing our users. And we push hard to make significant improvements such as those we provided for your feedback.

Lastly for any milestone feature issue you have an issue let me make this request. Please try creating a very small design and test the issue in isolation using MobiOne 2.0. If you have an app that you have used from 1.5>2.0M1>2.0M2>2.0M3>2.0 that has some issue please try rebuilding the entire application using 2.0 and test if the issue continues. For example you report that your receive an iOS dialog in the Test Center when your GotoURL fires and tries to open a URL in either a new or popup window. This was resoved in 2.0 and you should not see it. But you are required to regenerate the app code to see this new functionality.

[robert65]

Wayne as always i appreciate the work you guys do to get us the best working software to run our apps, i am still getting the goto issue during the build process and i have like yourselves put in many hours in getting my apps to the appstore, and to try a rebuild just felt a major step back, i will await your findings of the non responsive issue in 2.0, kind regards.

[robert65]

Wayne, update, i tried creating a new version now i get only one frozen tab on the home screen compared to the origional where 5 where frozen

[support-michael]

@robert65

I can replicate some of the behaviors you identified. I have been working to isolate the issue. I expect to know more tomorrow (Tue).

[Author]

Posts