FAQ

MATERIAL

• Big archive: If it’s a big FTP it can crash the FTP → ask Kenny if the amount is ok; 59GB was ok last time, depends on how much is already on the FTP —> might be that they would have to split it up, so they have to wait for our go
• How to set the earliest archive date: 
• Go to Superadmin
• Applications —> click on the application 
• Click on edit (next to the Application name) 
• Scroll down to Archive datepicker earliest date

APPLICATION 

Testing

Internal testing: 

• Internal testing does not require the app to be accepted (by Google/Apple)
• For iOS: We need the invited users to accept an invitation before we can invite them to test the app
• For Android: The invited users can access testing directly by clicking the link.

Custom tabs:

• Is it possible to add an email address in a custom tab? → Not possible, needs to be an actual URL (alternative: you can write a digital edition in prenly; you can create a banner (mailto link is possible)
• We can only display what is included in a link, if the pictures are not fetched in the feed, we cannot display them 
• We need the Https protocol; when you copy the url/when adding it there needs to be the https url in it
• Can we rename the „more“ button? —> No, it is not possible to rename the more button
  

Review process 

• Google PDF on the verification process for Developer Account

Possible to update after build with only new review:

• Android - all things related to the store:
• New name in Play (new review, no change in the binary)
• New description in Play (new review, no change in the binary)
• New screen shots in Play (new review, no change in the binary)
• New prices IAP (new review, no change in the binary)

Possible to update after build but requires new review due to changes in the binary:

• iOS - all changes
• Android - all changes related to the app:
• New name in unit, new app icon (change in binary = new review)
• TTS on or off (change in binary = new review)

Possible to update after build but requires new review due to changes in the binary and a new version:

• iOS - new version is required if the app already has the latest version and needs to be updated (same version can be reused if not released)
• Android - new version is required if the app already has the latest version and needs to be updated (same version can not be reused if the binary is uploaded, even if not released)

What can lead to rejection in the review process? / Which tasks have to be completed before HD can build the apps 

The tabs don't need an app update so that is perfectly fine to add later, however they should be included in the review, otherwise there might be some issues with later updates.
While the app is in review changes to the apps/custom tabs can lead to rejection 

PURCHASE

• Links to purchases - e.g. banner on home page that leads to a website where the opportunity to purchase can be easily found.
• Info text about purchases that can be found elsewhere
• Info about purchases in the descriptive text of the app
• Links for “subscription missing” at login

LINKS

• Apple: Link to Android
• Google: Link to iOS

CONTENT

• Too few issues published
• No cover images on editions (only happens when customer made own digital editions directly in Prenly and did not upload image)

FEATURES

• Features that are claimed to be in the app are not found during review, like: Text-to-speech

OTHER

• Age rating (must be present when app is sent for review)
• Category (must be present when app is sent for review)
• News text missing for News category
• App Privacy not specified
• Test account missing

INTEGRATION 

Remote API

• The customer needs to inform us, which “slug” should give access to which title 
• We don’t have a specific error code that indicates the user exists but is currently blocked. At the moment, there’s also no way to display a message to the user. 
• We send requests using the Content-Type “application/x-www-form-urlencoded”. In return, we need a response in “application/json” format.
• For simple format checks, you can use this test page: https://remoteapi.prenly.com/.

CSV file

• If you use email as customer id, you need a separate (second) email column, so that when you sign up as a reader, the account will automatically be connected 

Oauth2

• Redirect URLs: How to find BundleID for iOS and package name for Android
  • Go to Superadmin
  • Applications
  • Scroll down to clients and click on the iOS / Android application
  • In “Settings see:
    • google_package_name": "com.prenly.vestnik" or 
    • "apple_bundle_id": "com.prenly.vestnik"
  • Fill the bundle ID / product name into the URL in the Trello code

TOOLS

PWS

• Language in PWS: Start and archive and settings are depending on the language on the device —> but in PWS chose menu and change text for start and settings and so on and then it won’t change

Intercom

• Add contact in Intercom: All users —> Create user —> Create new —> Name & email —> Company name; Customer true; User tags English