- About Vivit
- LUGs & SIGs
- Vivit Blogs
- News & Events
- Knowledge Base
|HPE Software Products: Mobile Center|
Installation of MC fails...
I'm using Mobile Center 2.01 and UFT 12.54. I'm trying to make a script with an app, but when I use object spy to store the objects of the app it shows just "Device". The app was already installed in the device, but I have also tried to upload it from Mobile center (Not packaged).
The strange thing is that other apps already installed in the device are recognized ok.
I have tested the same app with 2 devices and it's the same behaviour.
The app is "Mi Vodafone" (https://play.google.com/store/apps/details?id=es.vodafone.mobile.mivodafone&hl=es)
Many thanks in advance
I am installing HP Mobile Center 2.01 on windows 10 machine.
After 56% installation completion, the system throws an error msg - Failed to install local psotgres database.
Repeated the installtion 4 times by cleaning up the previously created installtion folder. However it is aborting at the same step every time and hence not able to complete the installation. Please guide me to overcome this problem.
We are using Mobile center 2.0.1 licensed version with UFT 12.54.
In older versions of Mobile Center i.e 1.52 the same objects were getting identified as "Device.App.WebView.Page.Object".
In Mobile center 2.0.1 ,In our Object repository, we created the same heirarchy("Device.App.WebView.Page.Object") and found that the objects which were not recognised earlier using the 2.0.1 are getting identified successfully.
We tried recording option of UFT and found that the objects which are added to local repository during recording are getting highlighted and recognised in Mobile device successfully though they are added with "Browser.Page.Object" hierarchy.
The Object identification issue is observed only when we added the objects manually into the object repository.
I am using UFT 12.53 and HP Mobile Web browser, while spying an object through Object Spy the object properties are displayed with hierarachy Browser >> Page >> Object,.
In previous version of Mobile center same objects were getting identified by hierarchy Device>>Application>>MobileWebView>>Object. If i Spy any object in HP Mobile Web browser and check the browser Version it is displayed as Chrome.
We are testing a WebApplication on both Desktop browsers and Mobile browsers
1. So does that mean there wont be any device dependency while identifying any object through Object repository.
2. After 2.0.1 The scope of Device Id and Application identifier will be just to launch a device. Device ID and Application Identifier wont play any role in object identification when the object is added into the Object repository.
3. We are using BPT framework and we run scripts on multiple devices. While using MC 1.52 objects gets added into the object repository with "Device>>Application>>Mobileview" hierarchy. So when we will upgrade mobile center to 2.0.1, at that time we dont need this hierarchy in our Object repository? Will it support both the heirarchy (Browser>>Page and Device>>Application>>Mobileview)?
4. Can we use the same scripts and objects created on Desktop chrome browser on Android Mobile center web browser and Android Chrome browser and iOS device safari browser?
I want to generate mobile app (windows/ ios/ android) penatration testing report. How can i get these reports?
is is possible to generate report using 15 day trial version ?
I needed to update the license of HPMC and after doing it I was able to access HPMC site again but when I connect Android or IOS devices they keep the state "not available". I checked the logs and the connector log show multiple times this messsage:
[2016-12-21 16:41:50,162]       [qtp1039825477-18] [INFO] [HPMC-Filters] Request Path= /connector/validateVersion (CLS=c.h.m.filter.AuthenticationFilter)
[2016-12-21 16:41:50,162]       [qtp1039825477-18] [INFO] [HPMC-Filters] request come from: 127.0.0.1 (CLS=c.h.m.filter.AuthenticationFilter)
[2016-12-21 16:41:50,165]       [qtp1039825477-18] [WARN] [c.h.m.s.impl.DatPropertiesService] cant read from property file from classpath, using filesystem path '' (CLS=c.h.m.s.i.AbstractPropertiesServiceImpl)
[2016-12-21 16:41:50,182]       [qtp1039825477-13] [INFO] [HPMC-Filters] Request Path= /client/certificate/login (CLS=c.h.m.filter.AuthenticationFilter)
[2016-12-21 16:41:50,183]       [qtp1039825477-13] [INFO] [HPMC-Filters] request come from: 127.0.0.1 (CLS=c.h.m.filter.AuthenticationFilter)
[2016-12-21 16:41:50,241]       [qtp1039825477-13] [ERROR] [c.h.m.s.impl.CustomerServiceImpl] The certificate is not valid or expired ... (CLS=c.h.m.s.impl.CustomerServiceImpl)
Could be a problem with the license?
Please let me know
- Red Hat Enterprise 6.5
- Mobile Center 1.52 + Patch 1
Im trying to execute a test script using MJobile center. After launching the Application on device error syats "Connection with the Application Losy 1009"
I'm working with new ipas that I need to upload to HPMC. When I tried to sign them manually with HPMC Enabler command line (following the instructions in http://mobilecenter.hpe.com/Content/Package_HPMC_Enabler.htm) I found that the process fails because of an error in codesigning.
The thing is: I'm using the same provision profile and developer certificate that worked fine some time ago. I check the Keychain access seeing that the developer certificate is fine and also take a look at the provision profile in the apple developer site. Both seems to be correct.
How can I found more details of the HPMC Enabler process? is there some kind of extended log to enable in the signing process so I can have a better scope of the problem?
Let me know
Ps: I also tried the gui version of Enabler and obtained the same result.
- Red Hat Enterprise 6.5
- Mobile Center 1.52 + Patch 1
- HPMC Enabler 1.52p1
I have a Mobile Center 2.01 Server running on Windows, and a connector running on Linux (CentOS Essentials).
Please confirm that I have understood the install correctly:
1. Download the Linux Connector patch and run the .bin on the Linux machine as root. This ends with a message saying successful install.
2. Restart the Linux Connector and confirm that I can connect to and use Android devices. Connector version (from the dat folder) is 2.01.01.00.421.
I don't need to patch anything server side.
3. Download the patched version of HPMC Enabler. Run this to resign the iOS agent and launcher files.
4. Copy the agent and launcher files to the connector.
5. Restart the connector. Test with an iOS device running the latest version of iOS.
The Server version should be 2.01.2744.
I have installed Mobile center server 188.8.131.522 in my windows machine and connector in aother windows machine. Then repackaging my app ipa file using HPM enabler and its ready to be uploaded in server.
Now i can only see start and stop mobile center server option in my windows machine. How can i open the GUI of mobile center server and upload the regenerated ipa file in the server.
Also please let me know the steps to connect my ios device to the server installed.
Thanks in advance
HPE Mobile Center 2.01 Patch 1 has been released. The patch includes the following enhancements:
* iFrame support for native browsers
* Support iOS latest formal build 10.1.1
* Android 7 support
* Support MC Lab UI via Safari on MAC
* Defects fixing and stabilization
The patch is also available on the website below:
For the most updated product documentation, please refer to http://mobilecenter.hpe.com/docs
A common question we receive through our support channel is this: How can we prevent our devices from updating to the latest version of iOS?
Often, organizations wish to vet the latest iOS release, verifying that the business-related apps they use will continue to function properly on the devices used by their organization. By delaying the deployment of the latest version of iOS within their organization, they buy additional time to run these checks before green lighting the upgrade.
Mobile Center, we support iOS7 and higher versions and therefore provide our customers an ability to test their apps using those versions. But iOS devices are keeping and asking for an update, which is makes challenging to keep older iOS on the device.
To be clear, Apple does not currently provide any functionality, either within iOS, via MDM, or otherwise to purposefully prevent an iOS update. We have seen these common methodologies used by our customers.
Install tvOS Beta Configuration Profile
Installing the tvOS Beta Configuration Profile provided by Apple will block the update messages from appearing on iOS.
The tvOS Beta Configuration Profile is restricted to distribution among registered Apple Developers only. You can access the program at the Apple Developer Portal. You should also be able to find the tvOS profile freely on the web with a little work.
Block the Update Servers
Blocking communication with the Apple update servers at the company network level may also help prevent updates. By disallowing traffic to the update servers on the company network, devices will be unable to update themselves. The pitfall of this methodology is that the device will be able to update itself if it joins a different WiFi network or has a cellular connection.
The two update servers that we are aware of are: appldnld.apple.com and mesu.apple.com.
I have launched HP mobile center available in Amazon AWS market place. After starting the instance when trying to access the Mobile center server, we are observing "Your mobile center license has expired' error.
I am upgrading to Mobile Center 2.01, being careful to read the documentation as I go. I see that there is now an ALM version dependency. Could I ask why this is please? I have asked for our SaaS instance of ALM to be upgraded.
The iOS 10.0.2 release causes Mobile Center devices to become unresponsive. Is there an estimate on the fix?
Recently upgraded Mobile Center v2.0 to 2.01 as v2.0 was not supporting Android 7.
After upgarde the Android v7 is still not supported, but we also failed all iOS devices that were working fine prior to upgrade.
Now the iOS devices are connected, but we could not perform any action on the device.
Any thoughts on how this can be solved? Any experience with v2.01?
What’s new in the release?
If you have an Amazon account, you can now use an on-premise connector to expand your device lab to AWS Device Farm.
In addition to replay, tests can now be also recorded on the device's browser - Safari for iOS devices, and Chrome for Android devices.
You can use Spy and Highlight actions on test objects in your hybrid app.
Mobile Center on Linux servers now also supports record and replay of tests on native device browsers.
You no longer need to package hybrid apps when testing with Mobile Center.
Now you can open a device reserved by you remotely from the Lab Management console, while a test is running on the device. For example, when executing an Appium test on a device, you can now open and control the device from the Lab Management console while the test is running.
Mobile Center displays the latency between the client and the connector to which the device is connected. You can now optimize the performance of the remote screen viewer by selecting devices with lower latency.
Mobile Center now includes a crowd testing solution, so that you can test your app with a wider variety of people, in different real-world situations, and on a larger variety of hardware and software combinations than are possible in-house. Mobile Center's integration with Ubertesters enables you to monitor and manage yourmobile beta testing, and ensures an accurate, fast, and cost-effective testing process.
Mobile Center's integration with SafeDK allows you to scan your Android app to uncover its SDKs. Optimize the user experience by choosing the right SDKs to implement, based on developers’ community feedback, ratings, reviews, and a list of similar SDKs. The scan also highlights if a particular SDK in your app is not used, or has been deprecated.
You can now use an Android device as a proxy for communication between the Mobile Center server and the NV server when these servers are on different networks.
Mobile Center is now available on Amazon Marketplace.
Sprinter integration with Mobile Center 2.01 includes support for:
In TruClient tests, support was added for the WaitForObject End event for measuring transactions in hybrid applications.
With the new ALM extension for Mobile Center, you can run tests of your mobile apps directly from ALM. The tests access the mobile devices and applications from your Mobile Center server and post the test results in ALM.
static const char *ic_init(image_client *client, const char *host, int port,
ic_init(&c, "localhost", 8889, &exceptionCB);
here are having 8889 this is hard code value, but if we want to test application using multiple port numbers how to do.
I’ve added my webpack configuration to optimize the bundle size, please see the details as follows:
The former configuration divided the bundle into 4 chunks, below lists the chunks size.
This is still too heavy especially that I have to add my own development code and configuration to develop different use cases UI. The total files size is so big and it is not acceptable by the client to have all those files downloaded at the client side
Is there is any way to reduce and optimize this bundle file size?