2.0.3 Release

[Paddy Foran]

Alright guys, I'm sure most of you have seen the latest blog post about the problems I've had with 2.0.3. I thought the version I gave you guys was stable, but Jason poked holes in it. I'm trying to patch up those holes, but it's taking me too long, and I have other responsibilities I need to focus on. So here's my plan.

Jason, I'll be in touch with you soon to try and get a solid grasp on that error. I'm working on doing some radical changes to the backend that make the code cleaner, more unified, and therefore more stable. If I can't get them done by Friday, I'm going to release the 2.0.3 I gave you guys, and hope for the best. If I *can* get it done, I'll give it to you guys on Friday, and you can all play around with it for a week or so before I release it to everyone, to see if there's anything wrong with it. Either way, as of Saturday, I need to switch my focus to my other responsibilities and let android2cloud take a back seat until at least one of them is completed.

Sorry for the issues. If anyone else is experiencing trouble with the 2.0.3 Chrome extension they have, please do let me know.

Thanks for all your hard work,

Paddy

[Ahmed]

I've read Jason's post, though I've never had any problems with 2.0.3.
In fact, I'd say android2cloud is at its smoothest right now -- the
only problem I'm having is the phone not remembering the recipient's
identifier, and it's very tolerable. The Channel API speed makes up
for it actually.

Go on with your plan, and I hope you gain track of your time.

Thank you so much for the work you do, Paddy.

[Sam]

Hi Paddy,

Just thought to let you know that I was having problem with 2.0.2. Page sent from Android but it doesn't seems to show up on my Chrome browser but it's working now with the new 2.0.3!

Thanks for your time and efforts :)

Cheers,

Sam

 

[Paddy Foran]

Glad that the current 2.0.3 fixes the issue for you, Sam. I'm almost done with the 2.0.3 server implementation (cleaned things up some, moved them around, and hopefully got over this pesky link issue), so I'll be updating this and the client (Android, Chrome) code that uses it before Friday, I hope. If not, I'll be releasing what you guys are testing now as 2.0.3.

Thanks,
Paddy Foran