This update was to address a change Flickr made in their API which would cause Blogsy to crash when you tapped on the Flickr icon in the dock. And you could not set up new Flickr accounts. Now Blogsy works with the new Flickr API so this will no longer happen.
If you have previously set up a Flickr account in Blogsy and you tap on the Flickr icon in the dock then you will get kicked out of Blogsy.
Or if you try to set up a new Flickr account in Blogsy you will see the following error message.
“Oops, Flickr doesn’t recognize the “frob” this application is trying to use.”
The reason for these problems is that Flickr has changed their API. This means we have to change the programming in Blogsy to work with the changed API then submit Blogsy to Apple for their approval.
If you have a Blogger blog and have Blogsy set to upload to your blog’s media library (a Picasa account) don’t update Blogsy to version 4.3.3.
We just discovered a problem with uploading to Picasa. As soon as we have more detailed information I will add it to this post.
We figured out the bug and fixed it and submitted the update to Apple (Blogsy 4.3.4).
One workaround until this update comes out would be to use some other app (there are many free apps that upload to Picasa) to upload photos to your Picasa account. Then from within Blogsy you can drag in those photos from the Picasa dock item to add them to your post and publish your post.
Recently Tumblr changed their OAuth callback from “http://xxx” to “https:/xxx”. This means that if you tried to set up a Tumblr blog then Tumblr would send back an error. This update fixes that so you will be able to set up a Tumblr blog again.
Also, in a unique set of steps Blogsy was not stripping out some junk HTML that iOS adds when typing in the webview. We fixed that so now that junk HTML gets stripped out in that situation.
We added one other bug fix to this update. If you try to add a link by going into the iOS popup bubble (instead of the drag-in method) and manually entering the URL in the Link Settings menu this could cause Blogsy to crash if you follow a certain set of steps. We have fixed this in this update.
Apple takes about a week to approve updates so this update will be in the App Store in about a week.
Tumblr has changed their OAuth callback URL from “http://xxx” to “https://xxx”. This means Tumblr sends back an error when trying to set up a blog. You can see what happens in the following screenshots when trying to set up a Tumblr blog.
This only effects people trying to set up their blog. If you have already set up your Tumblr blog in Blogsy then you will not have a problem.
We have fixed this so now Blogsy will work with either OAuth callback url (http, https).
We are adding one other fix to this update and then we will submit it to Apple. Apple takes about a week to approve updates and once they do then the update with these fixes will be in the App Store. I will do another blog post as soon as we submit this update to Apple and will update that blog post when Apple approves it.
Apple has expedited the approval so you can now find Blogsy 4.3.1 in the App Store. Please update right away.
Updated 3/1/2014 (10:02 local time)
We are getting quite a few emails from users saying that after they update to the latest version of Blogsy (Blogsy 4.3) it crashes as soon as they tap on Blogsy to open it.
We need your input because we are not able to reproduce this problem. If we can’t reproduce it then there is nothing for us to fix.
Users have said that if they delete Blogsy off of their iPad then download it from the App Store again they no longer have the problem. But we don’t consider this a solution.
Obviously we did full testing before we submitted the update and didn’t have any crashing problem. But now people are reporting the following three crashes.
1) Trying to turn off the Blogsy footer causes a crash. We have already fixed this and it will be part of the next update.
2) Trying to add a self-hosted WordPress blog infrequently causes a crash. We have fixed this and it will be part of the next update. But this crash should be intermittent. So if you keep trying to set up your blog you should eventually be able to.
3) The instant crash mentioned above.
a) We installed Blogsy 4.2.9 on our iPad and created some local drafts.
b) We went to the App Store and updated Blogsy to 4.3. (The strange thing is that Apple updated it once to 4.2.9 then we had to update again to 4.3. Did anyone experience this? Multiple people have reported having this same experience. We are wondering if this is related to the problem. We don’t have any control over this so we will reach out to Apple about it.)
c) We launched Blogsy and did not experience the instant crashing problem. So we are not able to reproduce this problem.
There is no way to determine if everyone is experiencing this instant crash or if only some users are experiencing it. The fact that we cannot reproduce it would lead us to believe that not all users are experiencing this problem. So we need to figure out what is different.
Can you please email us as much detail as possible so we can get this fixed and submit the next version to Apple and ask them to hurry and approve it? If enough people provide information we may be able to find something that is common and it will help us track down the cause.
Our email address is email@example.com
a) What generation of iPad are you using?
b) What version of iOS are you running?
c) Is your iPad jailbroken?
d) Did you have any local drafts in Blogsy?
e) Did you have a post open that you were working on before updating?
f) Did you experience the double update that we experienced?
g) Any other details you can think of?
We are very sorry your are experiencing this problem. We are trying hard to figure it out.
Latest Information: 3/1/2014
We have now had about 30 people provide answers to the questions we asked above. Every question had variation in the answers so they don’t provide any information to reproduce the problem. We have also had emails from users saying they update and didn’t experience the instant crashing problem.
So here is the latest question and request.
1) Is your iPad a cellular version or not?
2) Can you send us the crash log? This may help us track down the cause.
1. Sync with iTunes Crash logs are transferred to iTunes whenever you sync your device. Plug in your device, and launch iTunes to complete the sync.
2. Retrieve the Crash Log Mac Users: Open Finder (found in the Dock) Click on the ‘Go’ menu at the top of your screen, and select ‘Go to Folder’ Type (or paste): ~/Library/Logs/ CrashReporter/MobileDevice/ Open the folder with the same ‘name’ as your device. (Note: your device name appears in iTunes on the left side, under ‘Devices’). You will see at least one item starting with ‘Blogsy’. Copy the latest one to your desktop. Send us an email (firstname.lastname@example.org) with that file attached. Windows Vista/7 Users Open any Windows Explorer Window (My Computer, My Documents, etc.) Enter %appdata%, and press enter Navigate to Roaming > Apple computer > Logs > CrashReporter > Mobile Device > *Device Name*. (Note: your device name appears in iTunes on the left side, under ‘Devices’) You will see at least one item starting with ‘Blogsy’. Copy the latest one to your desktop. Send us an email (email@example.com) with that file attached. Windows XP Users Locate your Application Data folder. To see instructions on how to find this folder, click here: eHow: How to access the Application Data Folder Navigate to Apple computer > Logs > CrashReporter > Mobile Device > *Device Name*. (Note: your device name appears in iTunes on the left side, under ‘Devices’) You will see at least one item starting with ‘Blogsy’. Copy the latest one to your desktop. Send us an email (firstname.lastname@example.org) with that file attached.
Google (the owner of Blogger, Picasa and YouTube) has changed the return value type of one parameter in their OAuth Authentication response. This means that when you go to set up a Blogger, Picasa or YouTube account in Blogsy then Blogsy will crash or never stop trying to fetch the setup menu. This should only impact trying to set up a new account. If you have already set up your account in Blogsy before Google made this change it should not impact you.
To be precise, previously Google used the number “1″ for the “verified_email” parameter when it’s valid in one of the OAuth Authentication responses.
But now they’re using string “true” for the “verified_email” parameter.
We have fixed this and now we are going to submit it to Apple and ask them to hurry and approve the update.
We tried to submit the update to Apple and got rejected. Here is a screenshot showing the rejection.
The reason for the rejection is that as of February 1st Apple requires all apps to be built with Xcode 5 and iOS 7 SDK. We have continued to build Blogsy in Xcode 4 because when we use Xcode 5 and the iOS 7 SDK Blogsy’s drag and drop functionality no longer works and also it causes Blogsy to crash on an iPad 2 running iOS 7 (we are guessing this is related to a memory limit).
So we have to figure out how to overcome these changes Apple made in Xcode and the SDK. And there is no way to block iPad 2 users running iOS7 from using Blogsy so we have to try to figure out a solution to the iPad2 problem if we build with Xcode5. We are not sure exactly how long this will take but until we can get this figured out we won’t be able to submit the update fixing the change Google made in OAuth.
I will continue to update this post when we have more details to share.
We guess that enough developers complained to Google about their sudden change in OAuth because Google has restored it to the way it was before. This means that you should be able to once again set up your Blogger blog, YouTube, and Picasa accounts in Blogsy.
We are continuing to work on the update mentioned above so Blogsy can be build in Xcode5. And in that update we will add some code so even if Google changes OAuth in the same way users will still be able to set up their accounts.
The following items are in this update.
1) TextExpander – TextExpander now works with the new methods TextExpander requires. To update your snippets there is a button in Settings -> General Settings -> “Refresh TexExpander Snippets”.
2) TextExpander – TextExpander now works on the Rich Side in Blogsy.
3) Copy & Paste – Very rarely iOS adds some hidden code in the copy & paste content. Typically the ascii codes are from 0 to 127. But the ascii code for this hidden code is 8232. Blogs do not understand this ASCII code when publishing through the API so the blog will send back an error code. Blogsy now strips out this ASCII code if it is found when pasting something in from another app or website.
4) Local draft images after update – When you update an app the address to the database gets changed. This means that after an update Blogsy can no longer find the display image to display it in the local draft. The post is actually fine and if you were to publish it the photos would appear in your post correctly. It's just that Blogsy is not able to display the images if the local draft created before the update had images from the iPad photo library in it. This update fixes this issue, so any updates after this one will no longer have this problem.
This is our latest update to fix a bug and to update a few things.
But before I get into the details of what is in this update I need to ask for feedback. According to the reviews in the App Store some people had some problems after our last update. We do a thorough testing before we submit an update and we would never submit an update if we were having any problems in our testing. So we really need people that have a problem to email us (email@example.com) and let us know the problem. We need the details so we can try to reproduce it and figure it out. Unfortunately Apple does not provide us with any way to contact the people leaving the review in the App Store so we can't contact them for details. And we are not having any problems here so there is nothing for us to look into or test.
I would also like to ask people to take a few minutes to leave a review. These reviews are the most important factor in determining sales for an app. If mainly the people that are leaving reviews are the ones having a problem then the sales plummet and we have trouble paying our bills. Sorry for being so direct about this but we have reached a critical stage.
Now, on to a happier subject. The following is what can be found in this update.
1) Flickr orientation update: As I talked about in a previous post, Flickr changed their API and this caused images that are in portrait orientation to be sized based on landscape orientation in Blogsy. We have figured out a way to program around this Flickr API change so this update fixes that.
2) TextExpander update: Apple forced TextExpander to make changes to their programming. The results of that are that all apps using TextExpander have to be updated. This only effects iOS7 users. In Blogsy you will now find a “Refresh TextExpander Snippets” button in the Settings menu. Settings -> General Settings -> Refresh TextExpander Snippets.
3) Squarespace 5 bug: Blogsy would crash the first time you tried to update a post to your blog. This is fixed.
4) Translation update: Two French words were incorrectly translated.
We have had a few people have their blog send back a 425 error with the following message. This account has two step authentication enabled. Please configure an application-specific password to use with this application.
This happens when the Google Authenticator plugin is being used on a WordPress blog but it has not been set up for support for
These are the steps to set up your blog in Blogsy if you are using the Google Authenticator plugin.
1) Sign into your WP-admin in a browser.
2) Go to the Google Authenticator Settings. In the WP Admin go to Users -> Your Profile and you will find the Google Authenticator settings.
3) Enable the App Password feature.
4) Click the “Create new password” Button. (See the screenshot below). It will give you some code like the following. “JB67 CX3K 4YQE KGKW”. Save you settings.
5) Use the code as your password when setting up your blog in Blogsy. (Ignore the empty spaces between the groups of characters so the password will look like this “JB67CX3K4YQEKGWK”.)