Post

4 followers Follow
0
Avatar

Strange subscription API behaviors in 4.0 app

Are there any updated guidelines for implementing the subscription API in a 4.0 app? There are a few behaviors that don't translate very well to the new reader environment. Here are a few of the issues I've come across: 

  1. The guidelines required a "close" link for people who don't want to sign in. In older versions of this app, closing the My Account window would return you to where you were before. Now, it just closes the account window and leaves you with an empty background. Is there another recommended or required "close" mechanism now that is less confusing to the user?
  2. Related, but more of a bug probably: the "My Account" window in my builds has shown a tendency to crash and not load the designated login page. The only remedy seems to be killing the app from the multitasking bar and relaunching. 
  3. After a successful login, the app doesn't seem to be checking for entitlements. It has received a valid session token, which is received and validated by the My Account url, but it doesn't refresh the library. Again, the only way to trigger the initial refresh seems to be to kill the app and relaunch. After that it appears to function as expected. 

 

Ian MacFarland

Please sign in to leave a comment.

9 comments

0
Avatar

Regarding your point no 3, we are experiencing the same issue. It will be very painstaking for the customers to make a force close after succesful login.

At the moment, if user log's in, he/she won't see any changes at all in the library until he/she force closes the app and restarts it.

Hans Lõugas 0 votes
Comment actions Permalink
0
Avatar

Any word on this from Mag+? I downloaded a new build today and the same problems are still evident. 

I did notice today that tapping the "missing issues" button does seem to trigger an entitlement check. But, even if it does restore missing issues from that, it still displays a "no missing issues" alert – I presume because there are no in-app purchasing issues to restore. So that's kind of confusing. 

Ian MacFarland 0 votes
Comment actions Permalink
0
Avatar

Hi,

I'm sending this over to the dev team so they can investigate.

Best regards,

Sara 

Sara C Glaser 0 votes
Comment actions Permalink
0
Avatar

Regarding #1: The new UI functions a little differently than the old one, and the My Account window is now a unique space, just like the Library and Store. So if users don't want to sign in, they simply tap another menu button to go somewhere else. The old behavior, where it jumped you from the store to the issue, and then popped up on top, was very confusing to many users, and now you can make a bigger sign-in page with clear instructions for users by using the full window there.

#2 Are you sure the page itself is not experiencing any difficulty and that the device has a solid connection? We have seen other apps where it loads fine, so we'd like to reproduce the error to investigate further if it's on the app side or the web view side.

#3 The app should check for entitlements when the users opens it, either cold or from background. It won't recheck the entitlements during the same session, to avoid excessive hits on the backend (many of our clients are charged per hit). Is that what it's doing, or it's not populating entitlements on first sign in? Are you sure the correct entitlement reply is being sent?

Mike 0 votes
Comment actions Permalink
0
Avatar

Regarding #1: If you want to redirect the user to another space you could use the new "space URLs". For example internal://library/open to take the user to the Library, internal://help/open for the Help issue, or internal://store/open to go to the store.

#2: If you still have this problem, could you attach screenshot and if possible crash and/or console logs to this thread?

#3: This is a known issue that has been fixed for any builds done in Publish on 2012-10-01 or later. 

Fredrik Gadnell 0 votes
Comment actions Permalink
0
Avatar

#3 Thanks for this comment, we take it from here that we should release an update as soon as possible.

Hans Lõugas 0 votes
Comment actions Permalink
0
Avatar

I still have to add a comment regarding issue #3.

In older 3.5 app entitlement check and library refresh works as expected, which suggests that correct entitlement reply is being sent from the subscription server.

But with current builds (October 9th actually) the app still doesn't refresh library after successful login.

Hans Lõugas 0 votes
Comment actions Permalink
0
Avatar

We can see now, that tHis problem is solved with the latest builds

Hans Lõugas 0 votes
Comment actions Permalink