Android Support Guide - Revision history

Anw: Categorisation

2024-08-08T12:11:37Z

Categorisation

← Older revision		Revision as of 14:11, 8 August 2024
Line 161:		Line 161:

	[[Category:Android]]		[[Category:Android]]
			[[Category:Technical Guides]]

Anw: Added tracing via Terminal ID; Added note re: upgrading ABSStudio components; Added cleardown of server logs (draft);

2024-01-16T12:37:31Z

Added tracing via Terminal ID; Added note re: upgrading ABSStudio components; Added cleardown of server logs (draft);

← Older revision		Revision as of 14:37, 16 January 2024
Line 70:		Line 70:

	"C:\Program Files\Barcoders\AndroidStudio\Android Connector.exe" --debug		"C:\Program Files\Barcoders\AndroidStudio\Android Connector.exe" --debug

			Once debug has been enabled, the log files may be searched for the terminal ID.

			{{Note}} We can clear (delete) the log file and it will recreate with no issues whilst still running.

			{{Note}} A single copy of the log file is added to by the server - it does not change or rotate every day or hour.

			A script is being investigated to copy and to cleardown old scripts - details will be added here and in the installation guide when available.


			Tracing terminal ID through Debug logs
			* Find the terminal ID in WCS Maintenance, using the Connected Users screen - copy the terminal ID (large characters with hyphens for Android devices)
			* Use this to filter the log file for everything for that terminal ID.


Line 83:		Line 96:

	To check the Server version, check the latest updated version number in the upgrade log.		To check the Server version, check the latest updated version number in the upgrade log.

			{{Note}} Upgrades to our software requiring upgrade to Barcodes ABS Server is an exceptional process.

			The install to both the Android ABS Studio Server and Android client must be rolled in or back manually.

			Never upgrade the ABS Server or Android app unless required by an upgrade.

Anw: Updated troubleshooting in Android support guide

2023-12-15T15:23:30Z

Updated troubleshooting in Android support guide

@@ Line 126: / Line 126: @@
 ** Check the command window.
 ** Check the server log.
 [[Category:Android]]

Anw: Updated troubleshooting in Android support guide

2023-12-15T15:20:08Z

Updated troubleshooting in Android support guide

← Older revision		Revision as of 17:20, 15 December 2023
Line 24:		Line 24:
	The Android version of the RDT program is installed in exactly the same place as the existing RDT program RDTMenu1.exe and is called RDTMeni1_Android.exe.		The Android version of the RDT program is installed in exactly the same place as the existing RDT program RDTMenu1.exe and is called RDTMeni1_Android.exe.


			=== Debug Settings ===

	In "C:\Program Files\Barcoders\AndroidStudio" there are two configuration files:		In "C:\Program Files\Barcoders\AndroidStudio" there are two configuration files:
Line 61:		Line 63:
	* Debug		* Debug

	Logging is exported to the command window of the application. ~~This~~ can be ~~changed to export to a file if required~~, ~~by changing the~~ "~~Start~~ Barcoders ~~Server~~" ~~shortcut.~~		Logging is exported to the command window of the application.

			Logging is also sent to the server log.

			Debug mode can also be enabled on the shortcut when running the ABSServer, e.g.

			"C:\Program Files\Barcoders\AndroidStudio\Android Connector.exe" --debug


			=== Versions ===

	When running the system, the Android application and the Android Server connector must be the compatible versions.		When running the system, the Android application and the Android Server connector must be the compatible versions.
Line 71:		Line 81:
	* Find Warehouse Terminal		* Find Warehouse Terminal
	* Check version		* Check version

			To check the Server version, check the latest updated version number in the upgrade log.


	== Troubleshooting Guide ==		== Troubleshooting Guide ==
Line 76:		Line 89:
	* Check can other Wavelink devices connect		* Check can other Wavelink devices connect
	** Proves system up and running		** Proves system up and running


	* Check error on device		* Check error on device
	** When using the app on a wireless device, the application being used is subject to the connectivity of the device to the network and to the application. If there are any issues with the network connectivity or the app cannot be accessed, the application will display the main screen, showing "Error Connecting". Ensure that there is a network connection, then advise hit any key on any physical or popup keyboard to reconnect.		** When using the app on a wireless device, the application being used is subject to the connectivity of the device to the network and to the application. If there are any issues with the network connectivity or the app cannot be accessed, the application will display the main screen, showing "Error Connecting". Ensure that there is a network connection, then advise hit any key on any physical or popup keyboard to reconnect.
Line 82:		Line 97:
	** If system selected then splash screen displays, then Error connecting to WCS		** If system selected then splash screen displays, then Error connecting to WCS
	*** Check WCS running - basic WCS issue		*** Check WCS running - basic WCS issue


	* Check Android Connector Window		* Check Android Connector Window
	** If not already running, use "Start Barcoders Admin" shortcut on Desktop, or "C:\Program Files\Barcoders\AndroidConnectorWindow\TermProtoTestWindow.exe"		** If not already running, use "Start Barcoders Admin" shortcut on Desktop, or "C:\Program Files\Barcoders\AndroidConnectorWindow\TermProtoTestWindow.exe"


	* Check command window open		* Check command window open
	** Command window will be named "Start Barcoders Server", or "C:\Program Files\Barcoders\AndroidStudio\Android Connector.exe"		** Command window will be named "Start Barcoders Server", or "C:\Program Files\Barcoders\AndroidStudio\Android Connector.exe"
	** Check Task Manager that it is running		** Check Task Manager that it is running
	** Start if not		** Start if not


			* Check license
			** Look at license.xml file
			** Shows users and expiration.
			** Note: This file cannot be modified as it is checked. Modifications will fail the check and the system will be useless.
			** Compare total number of users in the Barcoders Admin window - if there are connected devices up to the maximum, no more users can connect.


	* Check for versions		* Check for versions
	** Confirm version of Android connector version in server logs or in Upgrade log.		** Confirm version of Android connector version in server logs or in Upgrade log.
Line 93:		Line 121:
	** Confirm validity and compatibility of versions - check local project documentation.		** Confirm validity and compatibility of versions - check local project documentation.
	** Advise update device for compatibility		** Advise update device for compatibility


	* Check for errors in the server.		* Check for errors in the server.
	** Check the command window.		** Check the command window.

Anw at 14:52, 15 December 2023

2023-12-15T14:52:03Z

← Older revision		Revision as of 16:52, 15 December 2023
Line 8:		Line 8:
	Filesystem:		Filesystem:
	* "C:\Program Files\Barcoders" - the ABSStudio files		* "C:\Program Files\Barcoders" - the ABSStudio files
	* "C:\logs"		* "C:\logs" - contains:
			** barcoders_upgrade.log - the upgrade log
			** ACDebugLog.txt - the server log
	* "C:\data"		* "C:\data"

Line 87:		Line 89:
	** Start if not		** Start if not
	* Check for versions		* Check for versions
	** Confirm version of Android connector version in server logs		** Confirm version of Android connector version in server logs or in Upgrade log.
	** Confirm Android version on device		** Confirm Android version on device
	** Confirm validity and compatibility of versions - check local project documentation.		** Confirm validity and compatibility of versions - check local project documentation.
	** Advise update device for compatibility		** Advise update device for compatibility
	* Check for errors in the server.		* Check for errors in the server.
	** Check the command window		** Check the command window.
	** Check the server log.		** Check the server log.


	[[Category:Android]]		[[Category:Android]]

Anw: Added troubleshooting

2023-12-15T09:33:42Z

Added troubleshooting

← Older revision		Revision as of 11:33, 15 December 2023
Line 72:		Line 72:
	== Troubleshooting Guide ==		== Troubleshooting Guide ==
	=== Android device can't connect ===		=== Android device can't connect ===
			* Check can other Wavelink devices connect
			** Proves system up and running
	* Check error on device		* Check error on device
	** When using the app on a wireless device, the application being used is subject to the connectivity of the device to the network and to the application. If there are any issues with the network connectivity or the app cannot be accessed, the application will display the main screen, showing "Error Connecting". Ensure that there is a network connection, then advise hit any key on any physical or popup keyboard to reconnect.		** When using the app on a wireless device, the application being used is subject to the connectivity of the device to the network and to the application. If there are any issues with the network connectivity or the app cannot be accessed, the application will display the main screen, showing "Error Connecting". Ensure that there is a network connection, then advise hit any key on any physical or popup keyboard to reconnect.
			** If displays selection of system then does not show WCS splash screen:
			*** Check Android app set up properly in JSON config settings.
			** If system selected then splash screen displays, then Error connecting to WCS
			*** Check WCS running - basic WCS issue
	* Check Android Connector Window		* Check Android Connector Window
	** If not already running, use "Start Barcoders Admin" shortcut on Desktop, or "C:\Program Files\Barcoders\AndroidConnectorWindow\TermProtoTestWindow.exe"		** If not already running, use "Start Barcoders Admin" shortcut on Desktop, or "C:\Program Files\Barcoders\AndroidConnectorWindow\TermProtoTestWindow.exe"

Anw: Added Android Troubleshooting guide

2023-12-15T09:30:13Z

Added Android Troubleshooting guide

@@ Line 69: / Line 69: @@
 * Find Warehouse Terminal
 * Check version
 [[Category:Android]]

Anw: Categorisation

2023-07-17T08:17:50Z

Categorisation

← Older revision		Revision as of 10:17, 17 July 2023
Line 69:		Line 69:
	* Find Warehouse Terminal		* Find Warehouse Terminal
	* Check version		* Check version

			[[Category:Android]]

Anw at 14:45, 24 April 2023

2023-04-24T14:45:49Z

← Older revision		Revision as of 16:45, 24 April 2023
Line 60:		Line 60:

	Logging is exported to the command window of the application. This can be changed to export to a file if required, by changing the "Start Barcoders Server" shortcut.		Logging is exported to the command window of the application. This can be changed to export to a file if required, by changing the "Start Barcoders Server" shortcut.


			When running the system, the Android application and the Android Server connector must be the compatible versions.

			To see the Android app version, get the user to:
			* Go to Settings
			* Apps
			* Find Warehouse Terminal
			* Check version

Anw: Initial Creation

2023-04-24T14:43:40Z

Initial Creation

New page

== Android Support Guide ==

References:
* [[Installing Barcoders Android Server]]
* [[Android Usage Guide]]

Filesystem:
* "C:\Program Files\Barcoders" - the ABSStudio files
* "C:\logs"
* "C:\data"

Shortcuts should be created on the desktop:
* "Start Barcoders Server" - the server itself - should already be running
* "Start Barcoders Admin" - similar to Wavelink Administrator - shows the connected devices and licenses.
* "Start Barcoders Updater" - for updating the version.

The ABSStudio Server runs in a command window that must remain open at all times. Do not close this window as this will stop all Android functionality for that customer.

When Android devices connect, the processes will be running under the "Start Barcoders Server" - it is from here that they can be killed with Task Manager.

The Android version of the RDT program is installed in exactly the same place as the existing RDT program RDTMenu1.exe and is called RDTMeni1_Android.exe.

In "C:\Program Files\Barcoders\AndroidStudio" there are two configuration files:
* appsettings.json - application log levels
* config.json - the applications being run by ABSStudio

To configure applications that can be run by the system, add entries to the config.json file, example below:

{
"ProgramTasks": [
{ "ExecutablePath": "C:/WCSTEST/RDTMenu1_Android.exe",
"Name": "RDTMenu1 (TEST)",
"UsePipes": "True",
},
{ "ExecutablePath": "C:/WCSLIVE/RDTMenu1_Android.exe",
"Name": "RDTMenu1 (LIVE)",
"UsePipes": "True",
},
]
}

To change logging for the application, modify the Logging setting of the appsettings.json file, example below:

"Logging": {
"LogLevel": {
"Default": "Info",
"Microsoft": "Warning",
"Microsoft.Hosting.Lifetime": "Error"
}
},
Values can be changed to
* Info
* Warning
* Error
* Debug

Logging is exported to the command window of the application. This can be changed to export to a file if required, by changing the "Start Barcoders Server" shortcut.