-
Notifications
You must be signed in to change notification settings - Fork 101
Advanced FAQ
This is a list of advanced Frequently Asked Questions for Baker. If you cannot find your question, try with the Basic FAQ.
You might try, but it's there for a very specific reason: the delay we have there is exactly the time it takes to complete the animation. This means that if you remove that delay the user won't see the page before that time and also will get a very bad jittery animation because it will try to load the page at the same time of the animation (in the end, effectively delaying the loading).
A few developers are trying to port Baker to Android, but we still have not managed to test it. The most promising port is currently the friar project. A BakerAndroid project also exists, but it looks like it was abandoned.
Try adding an explicit CSS color rule for the body element, like this:
body {
background: white;
}
See issue #651 for more context.
Baker needs your server to return how big the file is in order to draw the progress bar (otherwise there's no way of knowing how close to completion the download is).
Make sure your server is returning a correct Content-Length
header for the download endpoint (e.g. the URL of your HPUB file).
This means that Baker has contacted the App Store to retrieve information about a given product (typically its price), but the provided product ID has not been recognised by the Store.
Double check that the product ID corresponds to the one you set up in iTunes Connect. If it does, make sure that the bundle ID for your app corresponds to the one in iTunes Connect.
This usually means that an App Store transaction is stuck in the processing queue and iOS is sending it to Baker over and over again, waiting for it to be acknowledged.
If you've set the PURCHASE_CONFIRMATION_URL
constant, make sure that the server is responding correctly: Baker will only acknowledge a transaction after the server has responded.
Make sure that your shelf contains at least an issue with a valid product ID.
Check the log for Invalid product identifier
errors and see the relevant FAQ for more info.
The logic deciding which issues to unlock is up to an external server. Baker will push purchase receipts to PURCHASE_CONFIRMATION_URL
and it will expect to find a list of unlocked issues at PURCHASES_URL
.
Make sure the two constants are set and that your server conforms to the Baker server API.
This could be due to a lot of different reasons, such as:
- The Bundle ID for your app is not configured correctly. Double check with the value in iTunes Connect.
- You are already logged in with a real user. Sign out from your Apple ID and sign in with a test user.
- The error is telling the truth: the device cannot connect to the Store. Check your connection and make sure the Store sandbox is not temporarily unavailable
You may get this alert when uploading your magazine to iTunes Connect. According to other app creators, this is not an issue: if you are not using push notifications, the app will be approved all the same. See issue 879.