EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB236171: Using a Configuration That Doesn't Specify User Credentials, the 9.4.1 Update 1 Android SDK App Crashes


Community Admin

• Strategy


Possibility to set up the MicroStrategy Mobile Android project by following the steps in the MSDL.

SYMPTOM:
It is possible to set up the Strategy Mobile Android project by following the steps in the MSDL.
 Setting up the MicroStrategy Mobile project
After setting up the project, you should be able to compile the project successfully using the default mobile configuration. 
To configure this app, there are two options:

  1. Use the Mobile Configuration URL
  2. Embed the Mobile Configuration to pre-configure Strategy Mobile 

Preconfiguring MicroStrategy Mobile
When the mobile configuration that is being used doesn't specify project or web server credentials, the application will crash with an error similar to this one:


03-23 10:24:14.169: E/AndroidRuntime(23223): android.content.res.Resources$NotFoundException: String resource ID #0x7f0900b9
03-23 10:24:14.169: E/AndroidRuntime(23223): 	at android.content.res.Resources.getText(Resources.java:274)
03-23 10:24:14.169: E/AndroidRuntime(23223): 	at android.content.Context.getText(Context.java:366)
03-23 10:24:14.169: E/AndroidRuntime(23223): 	at android.app.Dialog.setTitle(Dialog.java:544)
03-23 10:24:14.169: E/AndroidRuntime(23223): 	at com.Strategy.android.webapp.utils.CredentialsHelper$2.run(CredentialsHelper.java:225)

 
STEPS TO REPRODUCE:

  1. Set up the Strategy Mobile project
  2. Pre-configure StrategyMobile or use the configuration URL using a Mobile Configuration that doesn't specify credentials so that the user gets prompted.

The crash won't happen in all cases. This happens when the resource ID that is trying to be used doesn't exist. It is also possible that the resource ID is the wrong one. In this case, the app won't crash but the pop-up dialog asking for credentials won't have the correct label. 
CAUSE:
This is a known issue with 9.4.1 Update 1 Strategy Android SDK. 
ACTION: 
Contact Strategy Technical Support for more information.


Comment

0 comments

Details

Knowledge Article

Published:

July 21, 2017

Last Updated:

February 14, 2024