I have 2 real android devices and I used them to test my android app (I am new at Android programing)
When I clicked "run" button, the dialog box showed me two of my devices:
Table 4.2.2 and Cellphone 5.0
After running, my tablet launched the app perfectly, but my phone (5.0) wouldn't launch, it even wouldn't install new app, I tried many time, and finally it run, but at the later time, I needed to remove previous app to run new app.
Please help me to resolve this problem.
Well, you have to remove the old version of your app all the time? If yes, you should use a keystore file for signing the app (and always the same). My device also refused to update an app because I didn't sign it with a keystore file. (I have one device with Android 5.1.1 and one with Android 4.2.2, had the same issue with the 5.1.1 one until I signed it)
Related
I have noticed on iOS 15, when I install an app from TestFlight, my app icon is not appearing on the device. Only placeholder for app icon appears on physical device.
All app icon assets for every resolution are correctly added to Assets. The app icon appears in the test flight app and in appstoreconnect everywhere including TestFlight and builds.
The only place it doesn't appear is on the device. It appears normally on the simulator.
The only fix I found was to add a version of the app to add a build where you submit for review and save it. No need to submit. Then install from TestFlight and reboot device. The problem is as soon as I uploaded a new build to TestFlight it stopped showing icon and had to go through this silly process again.
I have never had this issue with past apps and wondering what the issue is and how to resolve it.
I encountered the same issue with testflight on iOS 15. I found this from apple developer forum that might of help:
https://developer.apple.com/forums/thread/682648
According to the accepted answer by #vladweinstein, a temporary solution is to restart the device after installing the app.
This works for me too.
We are still having the same issue with TestFlight apps (iOS 14.7 and iOS 15+)
The only solution we found is to restart the device as Raphael Rex mentioned.
When using the simulator under Xcode 11.3.1 and iPhones simulating iOS 13.3, the simulation does not behave correctly. It works correctly under simulator iOS 12.1.
I get no messages that I don't also get under the iOS 12.1 simulator launch.
The behavior should be when a user starts the app for the first time, he is redirected to the signin screen. Instead it goes to the main screen (grayed out because there is no data). I can navigate manually to the signin screen and signin normally (device registers and appears on my online server) but the app should start downloading the database required to work. It just sits there (no alertview that would normally launch the download). If I relaunch the app, it again starts at the main screen, however at this point an alertview should appear that no database is present. If I manually try to start the download (in a setup screen within the app), the progress bar that normally appears does not, just a label signifying what database is suppose to download.
All of this works properly on the iOS 12.1 simulator (Xcode 10.1) of the same type (iPhone 8 Plus).
Is this an Xcode 11.3.1 bug or iOS 13.3 problem. I have customers using iOS 13.1 without any problems on actual devices. I am on a new iMac running Catalina, is it possible its a security setting to allow database download?
I was facing the same issue and I move back to Xcode 11.3. Guess it was not a stable update at all.
I'm trying to play with NativeScript to create any simple android app. I've done step 1 from NativeScript's 'Getting Started' (setting up my osx environment) and right now, i have a barebones NativeScript app created with tns create and android platform added to it.
When running tns run android everything goes well and the final message before device debug logs (i'm not an android/ios/mobile dev so i assume that it's just some kind of debug log of what's going on connected device) is:
BUILD SUCCESSFUL
Total time: 11 seconds
Project successfully built
Using /Volumes/HDD/Users/michal/Workspace/Sandbox/tns_hello_world/platforms/android/bin/tns_hello_worl d-debug.apk
Successfully deployed on device with identifier '00099fbd72369f'
However, there is nothing going on my device after that. No app is being launched, no error message. Just completely nothing.
My setup is:
OSX 10.9.5
Java 1.8.0_45
Samsung GT-I9100
Android 4.1.2
Have you any idea what am i possibly doing wrong? Thanks in advance.
Your android device is not supported by NativeScript. Use device with Android 4.2 (API level 17) or newer. You can also try it on emulator.
Jan 2019
I verified in Android 8.1, it works fine.
First look, it looks like not working.
However, after changing the text "Play with NativeScript!" to "Hello world" in home.component.html, I could see the text. The homepage message ideally should say this.
After upgrading my iPhone 5 to iOS 7 beta, it seems I have to re-connect it to Testflight.
Unfortunately, I can't install the provisioning profile:
After selecting 'Reconnect Device', 'Install Profile', 'Install Now', the alert is 'Profile Installation Failed. You iPhone is not activated'
I tried to remove the previous profiles, clear Safari cache and reboot, but no success...
Short answer - Go to TestFlight directly on Mobile Safari and use the TestFlight CocoaPod.
We got TestFlight working on the latest iOS 7 build. The TestFlight "app" that installs doesn't work, but manually visiting the TestFlight site in Mobile Safari allows you to install the profile and load the app. Nothing special needed. It sometimes takes a few tries loading the profile to get it to actually load.
Also, loading our apps into TestFlight wasn't working, so we started using the TestFlight CocoaPod and it works great.
I got it working on an iPad mini running iOS 7 beta 5, that was previously used with testflight while running iOS 6. It seems that it will work under some circumstances. What I did:
Unregistered the device from its connected testflight user account (actually this step might be irrelevant)
Launched testflightapp.com from Safari, not from any icon placed on home screen. It has to be from Safari where the url bar is shown. From here I could install betas. However the device itself is not listed under any user and it is not activated. While trying to activate it, testflight app says the registering works OK, however it really fails.
So, it MIGHT work but it's clear that the people at testflight has some work to do.
More: I am unable to get it working with an iPhone 4 iOS 7 beta 5 at all. The iPhone has not previously been used with testflight and seems to require an activation through that profile (at testflight or Apple, not sure) but the activation fails and there's no app list coming up in Safari, just the activation sequence. The key here might be that the device must have been used with testflight before, while on iOS previous to 7.
It seems that using testflight with iOS 7 beta does not work and/or is not supported at the moment.
Not sure what happened here but I was using testflight with an iPad mini that had iOS6. When I just upgraded it to iOS 7, the testflight site loads on the device, however installs never process.
I found the answer of Lysann Schlegel most useful. After some experimenting, I found out that simply opening TestFlight from Safari works fine. Don't use TestFlight app icon.
I had the same problem. In my case after i connect my iphone with the xcode/ organizer beta it let me install again the apps.
Check in Settings if you have the Developer options.
I'm sorry to say that this is currently untested and is a only workaround, but try downloading the ipa file from the TestFlightApp "Share this build" link and use xcode to install it.
This link is normally provided to allow pre iOS4 users to install using testflightapp.com
Even if this works this workaround is probably unacceptable for a vast majority of beta testers.
I'd say also use the "iphone configuration utility" but I suspect that the current release does not support the iOS beta.
If this does fix the issue for people then it's some confirmation that it's mainly the OTA profile that's at issue.
I did a fresh install of iOS 7 beta 6 (it did not have any provisioning profiles before) and was able to load an app from TestFlight. Installing the provisioning profile failed from the web, but I was able to get the correct one onto the device through XCode's Organizer. Then I downloaded the app from TestFlight in Safari (not the little portal TestFlight app). It loaded up just fine.
I installed iOS 4.2 on my 2nd-generation iPod Touch last week. I tried running my application on the device through Xcode, but it didn't work (because Xcode didn't yet support iOS 4). To solve that, I installed Xcode 3.2.5 and the iOS SDK 4.2. Now I can get the app to run in the iPhone/iPad Simulator just fine.
However, I can no longer select "Device" from the menu at the top of the screen. It's a choice, but when I try to click on it, it never actually gets a check mark.
Because of this, I can no longer run the app on my iPod. The other (related) problem is that I can't choose "Build and Archive" from the Build menu anymore because the target is not a device.
Why is this happening? Do I need to change some settings in my project, or something with my device itself?
EDIT: Upon closer investigation, it appears that I can't select anything but the iPhone Simulator 4.0. Maybe there's something wrong with the project file.
Check that the base SDK is set to Latest iOS (currently set to iOS 4.2) for your Xcode project and your target's product, then perform a rebuild and see if your iPod is recognized.
Also try visiting the Xcode Organizer and see if it's asking for anything from your iPod. Typically Xcode will want to collect some data from devices whose OS receive updates, so it can update itself and install your apps on the updated OS properly.