Support Forum

Ask questions and get help from MobileTogether experts.
MobileTogether Product Information
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
View
Go to last post Go to first unread
Mimic  
#1 Posted : Tuesday, July 9, 2019 5:05:19 PM(UTC)
Mimic

Rank: Newbie

Groups: Registered
Joined: 7/8/2019(UTC)
Posts: 5
France, Metropolitan

Hello,

- My Test App Works great in MTD (simple CRUD with an external mssql db connector)
- After Deploy to the server and Generate the code for App Store (Android), the files seems to be OK
- When i build with Android Studio, no bugs with the APK
(ps : before, i have to desable the "default activity" choice i Android Studio)

but

- When i run The app with the virtual device in Android Studio, the app is realy downloaded but could not be launched

- idem directly with a android mobile, ( it s not on the home page but i try with the mobile file system app, and a message appears : could not be launch)...

Thanks for your help.

Michel

AFC  
#2 Posted : Wednesday, July 10, 2019 6:02:03 AM(UTC)
AFC

Rank: Administration

Groups: Registered, Administrators
Joined: 9/15/2014(UTC)
Posts: 71
Austria

Was thanked: 10 time(s) in 10 post(s)
Hi!

Why did you have to disable a default activity?
What did you change exactly? Without default launcher activity, an Android app cannot know what to start.

What's the error message in the "Build" or "Logcat" window?


Mimic  
#3 Posted : Wednesday, July 10, 2019 8:38:12 AM(UTC)
Mimic

Rank: Newbie

Groups: Registered
Joined: 7/8/2019(UTC)
Posts: 5
France, Metropolitan

Hello,

1/ no changes, but at the first try to build, the process dont recognize the default page.

Now the defaut page is ok and setting on 'am start cmd' , but the debug launch an unexpected error, see below

on my link : micro-hs

2/ ps : I dont understand if the app (downloaded from the store) must connect to the MT Server at each launch ? or the app can be completely autonome ?

Regards
Michel

AFC  
#4 Posted : Wednesday, July 10, 2019 10:14:59 AM(UTC)
AFC

Rank: Administration

Groups: Registered, Administrators
Joined: 9/15/2014(UTC)
Posts: 71
Austria

Was thanked: 10 time(s) in 10 post(s)
Hello Michel!

1) Please try to turn off the instant run (File => Settings => Build => Instance Run)
In case this does not help, please contact our Support team - we might need more information about your specific environment.

2) Per default, the MobileTogether App refreshes the solution list from the server on startup.
You can change this behavior on the client: Settings => Reload solutions on app start.
Also see here.

If a solution itself needs a server access when being started can be specified with the "Server Access" project setting.

Regards,
AFC
Mimic  
#5 Posted : Wednesday, July 10, 2019 11:48:46 AM(UTC)
Mimic

Rank: Newbie

Groups: Registered
Joined: 7/8/2019(UTC)
Posts: 5
France, Metropolitan

hello again

1/ No, even i turn off the setting : File => Settings => Build => Instance Run
that give the same error : "Unexpected constructor structure."

Ok i send that post to your support team

2/ Sorry im newbi, regarding your last answer, where i can find :
- Settings => Reload solutions on app start
- "Server Access" project setting.

Regards
Michel
AFC  
#6 Posted : Thursday, July 11, 2019 10:17:04 AM(UTC)
AFC

Rank: Administration

Groups: Registered, Administrators
Joined: 9/15/2014(UTC)
Posts: 71
Austria

Was thanked: 10 time(s) in 10 post(s)
Hi Michel!

reg. 2) As written in the mentioned link:
The Settings page

To access the Settings page, tap the Menu (or Options) key on your device and select Settings. The Settings page has two sections: General Settings and Added Servers.

General Settings

• List solutions with details: Displays a descriptive text below the solution name on the solutions page.
• Reload solutions on app start: Reloads all the solutions from the connected server whenever the app is started.

The last point is that one you should use.

And in the Project Properties:
Server Access
This option specifies the level of server access while the solution runs. The default is always.


• Always: Connection to the server is required in order to run the solution. The server is continually accessed while the solution runs.
• On Demand: The MobileTogether Client app runs the solution on its own; it connects to the server only when it needs to exchange data with the server. To run the solution, the app uses data in the internal $PERSISTENT tree, other persistent data, or embedded data. You can use the XPath function mt-has-serveraccess to check whether a server connection exists, and then use actions to save appropriately. For example, if no connection exists, then the data can be saved as persistent data on the client. As soon as a connection to the server is established, data can be saved to databases and/or files on the server.
• Never: The MobileTogether Client app runs the solution entirely on its own and without needing a connection to the server or any data from the Internet.


Hope this help,
AFC
Users browsing this topic
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.