Signiant app что это
Download the Signiant App
The Signiant App connects your computer to Media Shuttle allowing you to transfer multiple files at once via high speed transfer. Download the latest version of the Signiant App to take advantage of the latest updates for Media Shuttle and Signiant’s Transfer API.
Note: The Signiant App is only supported on one user account per computer.
Select the release of the Signiant App for your operating system.
The Signiant App automatically checks for updates every 12 hours. To force an immediate update, edit the SigniantClient.json file and delete the update-checked line. The Signiant App then checks for an update after the next file transfer. A notification is displayed when the update is ready for installation.
October 20, 2021: Version 1.3.1731 of the Signiant App includes a fix that resolves Signiant App crashes in unstable network conditions.
July 21, 2021: Version 1.3.1728 of the Signiant App includes a bug fix that resolves Signiant App crashes when starting a transfer on Windows.
June 15, 2021: Version 1.3.1726 of the Signiant App adds support for the Apple M1 processor and macOS Big Sur. This version also includes bug fixes and improves user interface notifications.
April 20, 2021: Version 1.3.1721 of the Signiant App includes improvements to app behavior and bug fixes.
March 5, 2021: Version 1.3.1717 of the Signiant App includes stability improvements and bug fixes.
February 19, 2021: Version 1.3.1714 of the Signiant App includes a security fix related to file selection.
January 18, 2021: Version 1.3.1710 of the Signiant App adds support for custom install locations and faster connections to storage. This update also includes bug fixes for new Signiant App installs and Microsoft Azure cloud storage.
October 13, 2020: Version 1.3.1703 of the Signiant App includes security updates, major performance and stability enhancements, bug fixes, and improved process management for Windows. This is a required update for all users. Users will be prompted to upgrade to continue using the app.
Beta releases of the Signiant App contain features still under development and are intended for members of the beta program.
September 23, 2021: Version 1.3.1729 of the Signiant App includes a fix that resolves Signiant App crashes in unstable network conditions.
July 21, 2021: Version 1.3.1728 of the Signiant App includes a bug fix that resolves Signiant App crashes when starting a transfer on Windows.
May 28, 2021: Version 1.3.1726 of the Signiant App adds support for the Apple M1 processor and macOS Big Sur. This version also includes bug fixes and improves user interface notifications.
March 16, 2021: Version 1.3.1721 of the Signiant App includes improvements to app behavior and bug fixes.
February 25, 2021: Version 1.3.1717 of the Signiant App includes stability improvements and bug fixes.
January 22, 2021: Version 1.3.1714 of the Signiant App includes a security fix related to file selection.
November 19, 2020: This version of the Signiant App includes performance improvements related to connection time and bug fixes for Microsoft Azure cloud storage.
September 28, 2020: This version of the Signiant App includes security updates and improved process management for Windows. This is a required update for all beta users. Users will be prompted to upgrade to continue using the app.
August 27, 2020: This version of the Signiant App includes bug fixes related to websocket locking, and performance improvements.
June 4, 2020: This version of the Signiant App offers improved security and enhances certificate logging.
Новый сервис Huawei позволяет запускать Android-приложения без установки
С тех пор, как Huawei запретили пользоваться сервисами Google, китайцы пытаются всячески минимизировать понесённые из-за этого потери. Сначала Huawei взялась перевыпускать уже существующие смартфоны под новыми названиями и с более продвинутым «железом». Это позволило ей продолжить устанавливать на них Google Play Services, потому что по документам это были не новые устройства, а старые, на которые санкции США не распространяются. Тем не менее, очень быстро стало понятно, что бесконечно долго на этом выезжать не получится и надо делать что-то на перспективу.
Huawei развивает свой магазин приложений, делая его похожим на Google Play
Читайте также: Сколько приложений работают с Huawei Mobile Services
Первоочередной целью Huawei было создать конкурентоспособный магазин приложений. Несмотря на то что у неё уже был каталог AppGallery, его предстояло наполнить софтом, чтобы он стал интересен не только китайской аудитории, для которой изначально и создавался, но и всем остальным. Это было сложной задачей, но Huawei, надо отдать ей должное, довольно неплохо с ней справилась и расширила ассортимент AppGallery настолько, что им даже стало можно пользоваться в России. А чтобы стало совсем здорово, китайцы решили позволить владельцам фирменных смартфонов запускать приложения для Android без установки.
Как запускать приложения без установки
Quick Apps доступен только в AppGallery
Механизм, который обеспечивает запуск приложений без предварительной установки, называется Quick Apps и, по сути, является аналогом Instant Apps от Google. Поэтому ограничения, которыми они связаны, у них примерно одинаковы. Из-за того, что софт не может сохранить в памяти устройства все свои файлы, то и его функциональность будет неполной. В результате, если вы попробуете запустить игру без установки, скорее всего, вам будет доступна только пара первых уровней, а для продолжения придётся произвести полную установку.
Тем не менее, Huawei уверяет, что благодаря Quick Apps пользователи смогут экономить пространство при использовании тяжёлых приложений, требовательных к ресурсам. Получается, что большая часть функций ПО, установленного таким образом, всё-таки сохранится, хотя это только предстоит проверить. Но, если китайцы действительно позволят пользоваться большей частью возможностей приложений из AppGallery, не устанавливая их, это будет прорыв.
Как работает Quick Apps
Несмотря на то что утверждается, что Quick App не требует установки приложения в принципе, на самом деле это не совсем так. Чтобы игра или программа запустились, необходимо, чтобы небольшой пакет данных всё-таки был загружен на устройство. Однако его объём чаще всего не превышает 3% от суммарного веса приложения, которое пользователь хочет опробовать. Это, во-первых, отличный способ сэкономить доступное пространство, если его немного, а, во-вторых, очень удобно в качестве продвинутого демо-режима. Активация Quick Apps происходит по нажатию на отдельную кнопку, которая располагается в интерфейсе рядом с кнопкой загрузки.
Читайте также: Huawei не вернётся на Android после запуска HarmonyOS
Прямо сейчас механизм Quick Apps доступен только на Huawei Mate 30 и Mate 30 Pro, потому что им действительно нужнее. Дело в том, что это единственные смартфоны компании, которые изначально несовместимы с сервисами Google, а потому их владельцам приходится обходиться собственными службами Huawei, во многом не дотягивающими до решения поискового гиганта. Впрочем, есть надежда, что совсем скоро китайцы развернут Huawei Mobile Services среди всех пользователей и тогда все мы сможем без проблем испытать Quick Apps в реальных условиях.
Before troubleshooting issues with older versions of the Signiant App, it is recommended that you upgrade to the latest version of the application.
Troubleshooting Signiant App Installation
You can identify possible problems with the installation of the Signiant App using three methods:
Check for the Signiant App in the Applications folder
If the application is correctly installed, Signiant App will appear in the Applications folder.
Check for messages that indicate installation
If the Signiant App is correctly installed the browser console displays messages confirming a connection to the Signiant App. If some of these messages are missing, it could indicate that the browser is not successfully connecting to the Signiant App.
To check for typical messages in the browser console:
Reset App Detection Cookie
Media Shuttle and the Web Transfer API (TAPI) set a cookie in your browser once they successfully connect to the Signiant App. The cookie is used by Media Shuttle to adjust behavior, such as wait intervals, when connecting to the App for the first time.
You can prompt Media Shuttle to detect the installation of the Signiant App by deleting the SigniantAppInstalled cookie from the mediashuttle.com domain in your browser. For those using the Web Transfer API, the domain will vary. When the portal is refreshed, the user should see the I have the App/Download the App message.
Note: See your browser documentation for the location of cookies.
Uninstalling and Reinstalling the Signiant App
If you determine that the Signiant App is not successfully installed, uninstall and reinstall the application using the latest version of the Signiant App.
To uninstall and reinstall the Signiant App:
When you visit the portal again you will be prompted to download and install the latest version of the Signiant App.
Checking Protocol Handler Function
Both Media Shuttle and the Web Transfer API request that the computer launch the Signiant App via a protocol handler call. When a browser receives a protocol handler call, it typically prompts a user to confirm that the computer should launch a specified application. Browsers often give users the option to remember the setting so that they do not have to answer the prompt each time the browser issues a protocol handler call.
To determine if the browser is sending a request to connect with and/or launch the Signiant App, you can temporarily remove the Signiant App from the protocol handler, requiring that the end user confirm the application launch each time.
To remove the Signiant App from the protocol handler:
Safari does not offer the option of launching the application without a prompt. Safari is not recommended for long-running transfers because of possible network disconnection issues when communicating via PubNub.
Checking Network Permissions
Administrator rights are not required to install the Signiant App but your network may have restrictions.
To verify network permissions:
In Settings > Security & Privacy, ensure that Allow apps downloaded from is set to Anywhere or Mac App Store and identified developers.
If you have a proxy enabled on the workstation, disable it and run the installer again.
Note: Disabling the proxy may only be possible if it is not required for a firewall.
Addressing Installation and Updating Issue on Parallels
To prevent this error, disable Coherence Mode application sharing and ensure that Share Mac applications with Windows is not enabled.
Addressing Constant Prompts for Installation
The end user may repeatedly see prompts to download the Signiant App, even when the application is installed. This problem may occur if:
If multiple versions are installed, uninstall all versions and reinstall the latest version of the Signiant App.
The Failure to initialize messaging service error may appear when you open the Developer Console if the Signiant Client process cannot communicate with the Signiant User process. The error may occur if the Signiant User process did not update, or if there is improper formatting of the loopback address in the hosts file.
This issue may prompt specific errors in the SigniantClient.log:
Connection refused from invalid IP address: 127.0.0.1
asio: error in WS handler: invalid state
Note: The Signiant App saves logs for the previous seven days. The application appends older log files with a number, e.g. SigniantClient.log.1.
If either of these errors appear in the log, change the loopback address in the hosts file.
To change the loopback address:
Troubleshooting Signiant App Transfers
Before proceeding with troubleshooting, ensure that the portal has been refreshed/reloaded.
Verifying that Required Ports and External Domains are Available
Signiant App transfers may fail if the ports needed for inbound and outbound traffic, as well as the external domains the Signiant App uses, are not accessible. For a list of required ports and domains, see Media Shuttle System Requirements.
Example Errors:
#### PubNub cannot be reached
Ensure that \*.pubnub.com and \*.pndsn.com are allowed through company firewalls.
#### Websocket ports are all busy
Look for errors in the SigniantUser.log file. The errors should appear even at the default log level.
e.g. [WSBrowserListener-WARN] Failed to listen to all WebSocket ports in the configured range: [10004, 10005, 20004, 20005]
The Signiant App needs only one of the ports to establish a WebSocket connection. At least one of these ports can be made available by closing another application that is using it.
Verifying that a Local Port is Available for Communication
The Signiant App may be unable to connect to its components if installed software uses the same local port as the Signiant App for communication.
To change the local port number:
Checking Network Connections
If an end user’s network is disconnected or frozen, the end user may see a spinning Signiant logo that does not allow uploading or downloading of content.
To check network connections:
Collecting Details on a Failed Transfer
If the required ports and external domains are accessible but transfers are still failing, additional information should be collected and analyzed.
There are three methods of collecting details on a failed transfer:
Contact Admin Prompt
When a transfer fails, the user is prompted to contact the operations administrator. When the user clicks on the Contact Admin link, they can enter additional detail about the transfer before the message is sent.
Developer Console Inspection
You can troubleshoot the Javascript code in your Developer Console. The location of the Developer Console will vary depending on your browser.
Transfer events and errors can also be found in the Developer Console if a transfer was done on that tab. This information is cleared when the web page is refreshed.
With the newest versions of the Signiant App and the Web Transfer API, there may be websocket errors caused by the way the application and the API communicate. If the Received Session Ready from App (via websocket) or Received Session Ready from App (via pubnub) message appears, the Signiant App & the Web Transfer API should be connected successfully.
Locating the File Picker
The file picker can occasionally end up behind other windows. If clicking on Add File or Download has no effect, but the Signiant icon does not indicate that the page is having issues, look for the file picker behind other open windows.
Note: You can view all open windows using Mission Control.
Before troubleshooting issues with older versions of the Signiant App, it is recommended that you upgrade to the latest version of the application.
Troubleshooting Signiant App Installation
You can identify possible problems with the installation of the Signiant App using three methods:
Check for messages that indicate installation
When the Signiant App is correctly installed, certain messages are logged in the browser’s console panel when a user opens portal pages. If some of these messages are missing, it could indicate that the browser has not successfully made a connection to the Signiant App.
To check for typical browser messages:
Check for Signiant App in installation directory
If the application is correctly installed, its components will appear in the installation directory.
To check that the Signiant App is located in the installation directory:
Prompt detection of Signiant App installation
Media Shuttle and the Web Transfer API (TAPI) set a cookie in your browser once it has successfully connected to the Signiant App. The cookie is used by TAPI to adjust behaviour, such as wait intervals, when connecting to the App for the first time.
You can prompt Media Shuttle to detect the installation of the Signiant App by deleting the SigniantAppInstalled cookie from the mediashuttle.com domain in your browser. For those using TAPI, the domain will vary. When the portal is refreshed, the user should see the I have the App/Download the App message.
Note: See your browser documentation for the location of cookies.
Uninstalling and Reinstalling the Signiant App
If you determine that the Signiant App is not successfully installed on the end user’s machine, uninstall and reinstall the application using the latest version of the Signiant App.
To uninstall and reinstall the Signiant App:
Note: Reinstalling the application will revert the Signiant App configuration file to its default settings. Any modified debug settings will have to be re-applied.
Checking Protocol Handler Function
To determine if the browser is sending a request to connect with and/or launch the Signiant App, you can temporarily remove the Signiant App from the protocol handler, requiring that the end user confirm the application launch each time.
To remove the Signiant App from the protocol handler:
Checking Network Permissions
The Signiant App is installed in an end user’s own AppData folder, for which they have all necessary write permissions. In some tightly-controlled networks, users may be restricted from installing any program.
The Local Security Policy editor allows network administrators to review and edit policies for a wide range of security permissions for your Windows machine. Rules defined here control who can install programs and the locations from which installers and programs can be run.
To check group policies, navigate to Security Settings > Application Control Policies > AppLocker.
Checking Registry Settings
Ensure that the User Shell Folders in your machine’s Windows registry are set to use %USERPROFILE% instead of a network location. The end user may not have access to the network location.
To change the user shell folders setting:
The protocol handler setting is also stored in the registry.
To check the protocol handler setting in the registry key:
If you have a proxy enabled in the Internet Properties on your machine, disable it and run the installer again.
Note: It may only be possible to disable a proxy if it is not required for a firewall.
Enabling Debug Logs for Signiant App Installation
If the Signiant App will not install with the EXE, you can download the MSI version of the installer and capture detailed installation logs.
To capture installation logs:
Troubleshooting Signiant App Transfers
Before proceeding with troubleshooting, ensure that the portal is refreshed/reloaded.
Verifying that Required Ports and External Domains are Available
Signiant App transfers may fail if the ports needed for inbound and outbound traffic, as well as the external domains the Signiant App uses, are not accessible. For a list of required ports and domains, see Media Shuttle System Requirements.
Example Errors:
#### PubNub cannot be reached
Ensure that *.pubnub.com and *.pndsn.com are allowed through company firewalls.
#### Websocket ports are all busy
Look for errors in the SigniantUser.log file. The errors should appear even at the default log level.
e.g. [WSBrowserListener-WARN] Failed to listen to all WebSocket ports in the configured range: [10004, 10005, 20004, 20005]
The Signiant App needs only one of the ports to establish a WebSocket connection. At least one of these ports can be made available by closing another application that is using it.
Checking Network Connections
If an end user’s network is disconnected or frozen, you or the user may see a spinning Signiant logo that does not allow uploading or downloading of content.
To check network connections:
Verifying that a Local Port is Available for Communication
A grey task bar icon indicates that the Signiant App is properly installed but unable to connect to its components. This may occur if installed software uses the same local port as the Signiant App for communication.
To change the local port number:
Addressing Failure to Initialize Messaging Service
This error may appear when you open the Developer Console if the Signiant Client process cannot communicate with the Signiant User process. The error may occur if the Signiant User process did not update, or if there is improper formatting of the loopback address in the hosts file. This failure may also be indicated by a grey taskbar icon or a spinning Signiant icon during a portal upload or download.
This issue may prompt specific errors in the SigniantClient.log:
Connection refused from invalid IP address: 127.0.0.1
asio: error in WS handler: invalid state
Note: The Signiant App saves logs for the previous seven days. Older log files have names appended with a number, e.g. SigniantClient.log.1.
If your machine has redefined the IP address for localhost, change the loopback address so that localhost routes to its default IP address ( 127.0.0.1 ). Admin privileges are required to modify Windows system files.
To change the loopback address:
Collecting Details on a Failed Transfer
If the required ports allow traffic but transfers are still failing, additional information should be collected and analyzed.
There are three methods of collecting details on a failed transfer:
Contact Admin Prompt
When a transfer fails, the user is prompted to contact the operations administrator. When the user clicks on the Contact Admin link, they can enter additional detail about the transfer before the message is sent.
Developer Console Inspection
You can troubleshoot the Javascript code in your Developer Console. To open the Developer Console, press the F12 key on your keyboard and select the Console tab to view the Javascript code.
With the newest version of the Signiant App and TAPI, there may be websocket errors caused by the way the application and TAPI communicate. If the Received Session Ready from App (via websocket) or Received Session Ready from App (via pubnub) message appears, the Signiant App & TAPI should be connected successfully.
Transfer events and errors can also be found in the Developer Console if a transfer was done on that tab. This information is cleared when the web page is refreshed.
Note: In Internet Explorer, reload the page again to see log messages from a page load.
File Picker Does Not Appear
The file picker can occasionally end up behind other windows. If clicking on Add File or Download has no effect, but the Signiant icon does not indicate that the page is having issues, look for the file picker behind other open windows. Alternatively, click Alt-Tab to toggle through the open applications and look for the one titled FileSelectDialog.
Configuring the Signiant App
You can configure the Signiant App by editing parameters in the SigniantClient.json file.
The location of the SigniantClient.json file varies depending on your operating system:
macOS:
/Library/Preferences/com.signiant.SigniantClient.json
Windows: %APPDATA%\Signiant\SigniantClient.json
Note: Do not modify the SigniantClient.json file unless directed to do so by Signiant Support.
When making changes to the Signiant App configuration, it is recommended that you make a copy of the original configuration file. Upgrading to a new Signiant App version does not modify any changes made to the configuration file.
If there are formatting errors in your edited configuration file, an invalid JSON error will be returned. The Signiant App will discard your modified configuration file and replace it with a default configuration file in the proper format.
Note: Parameter names are case-sensitive.
log-level
Sets the level of log detail and any log-level-overrides using the Signiant App component processes. For more information, see Collecting Debug Transfer Logs.
rest-server
Identifies the server used to send and receive REST API calls using the Signiant App.
token
Displays the automatically generated token used to authorize Auto Delivery uploads and downloads. This value is set by the Signiant App automatically, and is removed when Auto Delivery is disabled.
wsbrowser-port and wsbrowser-setting
Displays the received values from the Signiant Communications Service that configures the ports, domains, and details required to transfer files. These values are set by the Signiant App automatically.
udp-ip-mtu-size Set the maximum packet size, in bytes, for Signiant App transfers. The default and maximum value is 1472 bytes. Reducing the packet size is recommended on macOS deployments where the Signiant App is running on a VPN or network that has a reduced maximum packet size.
The following parameters can be added to the SigniantClient.json file and configured as required.
record-transfer-events
Saves a log of performance statistics to a local txt file. The txt file name includes the transferId. The log tracks time-stamped events for each user-initiated and automatically-generated transfer.
The log saves to the application’s perf folder:
macOS:
/Library/Application Support/Signiant/perf
Windows: %APPDATA%\Signiant\perf
Manifest files save to the Manifest folder, which is named for the transfer’s transferId property:
macOS:
/Application Support/Signiant/Manifest
Windows: %APPDATA%\Signiant\Manifest
unique-id
Defines an extra key to identify a machine as unique in special cases, such as when cloning a machine from another. The usual method to identify each machine for saving its Auto Delivery configuration may generate the same identifier for both machines. You can set this parameter to any text string, which will append to the usual identifier to ensure each machine’s Auto Delivery configuration is unique.