Big 3.2 crash: r3651-ios should probably take care of it, but we need more user feedback

Another approach to this: https://github.com/koke/wordpress-ios/commit/f1a06916bfdc82fe7f0dff2cc44b9c7322e6980d
Instead of just eating up whatever XML-RPC returns, we convert it to the data type we expect, or otherwise set it too nil. Do you think that’d be useful or is it too much?

Created a 3.2.1 milestone. Need to include updated translations and fix the startup crash.

http://ios.trac.wordpress.org/ticket/1466
http://ios.trac.wordpress.org/query?group=status&milestone=3.2.1

I’ve been modernising the codebase and updated libraries: modernize-3.3, cocoapods

• Migrated to ARC
• Started using CocoaPods
• Replaced some obsolete code (performSelector: and friends)

Please, don’t commit to trunk until this is merged, or I’ll spend a week crying in front of conflicts 😉 Use patches, local branches, push to github,… or just ping me to merge this

A few things I want to do before merging:

• More testing (this is the only real blocker, the next can happen on trunk)
• Merge our xmlrpc streaming changes with the new streaming upstream branch, and get XMLRPCDataCleaner into master
• Consider dropping Facebook SDK for iOS5 and use the iOS6 Facebook framework
• Remove viewDidUnload methods (deprecated in iOS6)

Headsup: changed the “newui-3.1” Component to now be called “User Interface” since there’s a need to tag tickets as relating to the overall UI and/or graphics only.

Tickets previously tagged with “newui-3.1” should now be tagged “User Interface”. Example: http://ios.trac.wordpress.org/ticket/1458

Translated everything remaining in 3.2 to Swedish. Should make it into the next update.

We really should provide some more comments for every new string that we add though, it’s painful trying to figure out how and where and why a string is being used. There were also a few instances of strings that are redundant.. Very similar to older strings or with just capitalization differing. One instance of the exact same string being it’s own entry and then as a part of another string but as a whole sentence. e.g. “Couldn’t connect.” + “Couldn’t connect. Try again?” – not this, but something along those lines. Painful for translating.

Seems as if iOS 6 could be breaking stats. This is unrelated to WPiOS 3.2 as a release, but something we have to look into asap. Doing support I’ve noticed that quite a few report extreme delays in stats updates in app – it may be because the cache is never cleared.

See this thread: http://ios.forums.wordpress.org/topic/statistics-not-updating

cc @kokejb

Testing time!

For folks who can install the latest builds, please take a moment to take our survey and help test out WPiOS 3.2.

Below is a list of devices, OSs and WordPress versions that we need help testing. If you help test, please check off the relevant box so we can get the best coverage.

oSs / Device combos

• iOS 4.3 – iPhone (any) (@kokejb)
• iOS 4.3 – iPad (any)
• iOS 5.0 – iPhone (any)
• iOS 5.0 – iPad (any)
• iOS 5.1- iPhone (any) (@aerych)
• iOS 5.1 – iPad (@irbrad)
• iOS 6.0 – iPhone (any) (@irbrad)
• iOS 6.0 – iPad (any) (@aerych, @irbrad)
• iOS 6.0 – iPhone 5

If you’re testing a particular device let us know here:

• iPod Touch 4th gen (@kokejb)
• iPod Touch 5th gen
• iPhone 3Gs
• iPhone 4 (@aerych)
• iPhone 4s (@irbrad)
• iPhone 5
• iPad (@aerych)
• iPad 2 (@irbrad)
• iPad 3 (@aerych)

Lastly, let us know if you test an older version of WordPress. (Probably testing the minor releases is good enough.)

• WordPress 3.0 (oldest supported) (@aerych)
• WordPress 3.1 (@danroundhill)
• WordPress 3.2 (@danroundhill)
• WordPress 3.3 (@danroundhill)

Thanks!

In #1327-ios, I’ve bumped the “required” version to 3.1 instead of 3.0. It’s just a warning, so older sites would still work the same as they did before.

Should we require a higer version? Why not just the latest stable?

If you’re interested in contributing, this little ticket is a great place to get your hands dirty: http://ios.trac.wordpress.org/ticket/1394

Sounds for 3.2 update! Attn @jmobb

After discussing the sounds and getting a feel for them in the app over the last few weeks, a few things:

• Notification sounds is going to be important to figure out. As per our previous thread a mix of tracks “Cheerful 1” and “Neutral 1” may be a good way to go. Can we get something like this to listen to?
• Sounds for swiping panels is too much. After using it for some time it became annoying. Two ways we can go about it instead:
  1. A subtle “click-pssh” sound when opening a new panel fresh but none when dragging.
  2. A sound for clearing panels (essentially we’d then have sounds for opening/closing panels but nothing in between).
• Pull-to-refresh sound works well, but I’m personally missing a “completed” sound – so pull is one, “locked in/refreshing” is one, “completed refresh” is one. The last one could potentially be played when the refresh panel slides down too if we want to do it that way, so there’s one sound for sliding up and one for sliding down.

Overall I think we’re very close. Excited to have these go in version 3.2.