As the Title Show , New version database Inpector Will lead my app crash and Only show this:
For security reasons offline mode is disabled when the process being inspected does not correspond to the project open in studio or when the project has been generated from a prebuilt apk.
if restart and noever open the database tab .it was nomal . this problem Temporarily only happens on Huawei phones
Yes, it is. I've confirmed this!
Related
I update my android studio to 3.1.3 but I cannot use platform 27 now
when I click "install platform and sync project" it pop up a download window and then disappear. But the error still exist. SDK Platforms is following:
expand SDK:
For anyone get this issue, you should uninstall Android SDK 27 then re-install it from SDK download manager.
#TrongHiue's answer didn't work for me. (Mac user, Android 3.2.1).
I had to close the IDE, go to Library/Android/sdk and rename the 'sdk' folder to 'sdk2'. Then reopen Android Studio - it will prompt you to tell you it can't find the old sdk folder but will automatically use sdk2. Hit ok. Then, let Android Studio re-index. It will now find platform 27 and you should be able to launch your app.
If you want to change your sdk folder back from skd2 to sdk, close the IDE, rename back to 'sdk', re-open the IDE, update the SDK location in File -> Project Structure, and make sure local.properties is pointing to 'sdk' folder and not 'sdk2'.
In my case, I fixed it by click "Edit" (Next to Android SDK Location) and install SDK platform at SDK Setup window.
Click here to see image
For me neither options worked.
I've updated to SKD 29 and Android Studio 3.6.
What did help was going to the SDK Manager and click the "Edit" link next to Android SDK Location. In the next screen you will see a message saying that an existing Android SDK was detected and only missing or outdated SDK components will be downloaded. Click Next and problem solved!
Ran into same problem but with API 26 and (win) studio 3.5.1. XavierDominguez solution was close to what I had to do to fix it. Close IDE, renamed Sdk to Sdk2, reopened studio, problem persisted so closed IDE, renamed it back to Sdk, reopened and worked this time around. Posted in case someone ran across same problem.
This usually happens when popup for update tools and you click on Update and after some time before finishing Update you Cancel It.
Simply Go to FIle--> Invalidate Caches/Restart
This can happen when your sdk location directory has space in it.
Change directory without space and re-build the project. It worked for me.
Old SDK Location: "C:\Users\DELL 15\android-sdks"
New Location: "C:\Users\android-sdks"
For the icon change effect on the android emulator and device if i install manually .apk .ipa file . It works fine after changing the application icon and uploaded mobilefirst console in the production environment.
but problem is marketing manager mail me . application updated but not changed the Application icon in iOS and android device.
at this situation what can i do ?
I flowing this
link
It is not clear to me whether you refer to the icon that you see on the device home screen or to the icon that you see in the AppCenter console.
The icon on the home screen is managed by the device OS, and Idan's answer is correct here. This effect has nothing to do with IBM AppCenter but rather with the device OS.
The icon in the IBM AppCenter console is cached for 30 minutes in the browser, in order to allow the browser to refresh the screen more quickly. The idea is that icons change rarely and speed it important. There is a Java VM property ibm.appcenter.services.iconCacheMaxAge (in seconds) that can be set to a different value to modify this effect.
Based on the comments, an update will not take place if you did not increment the version number of the application.
If you change a native resource such as the app icon, but do not increment the application version number then the check for a new version will not see the update because it is basing it on the version number.
Update the version number and upload the updated .apk and .ipa; the update should then happen.
First off let me be clear. I have several iOS devices. On the devices that have 7.0.6 I have no issues. When I updated one of the devices to 7.1 I'm having an issue. Let me explain.
On the iOS device that has 7.1 I navigate to the workbench URL and then I go to Manage applications and select install. I then get this message "Cannot install applications because the certificate for >ip address< is not vald. This process works on devices that have 7.0.6. I'm assuming there are issues with the new iOS update.
Now I did some searching and I found something that said there's an issue when trying to download an app from a HTTP site, so I changed a Web Reports setting (found in Eclipse Preferences -> Test -> Performance Test Reports -> Web Reports) to "Security is required to access reports". Thus it changed the port number to "8443". I then navigate back to the workbench URL using the https : // ip:port and try to install the app again. This time it just says Cannot open.
Any ideas on this?
Here is a workaround to be able to test with iOS 7.1
1) Get the zip of instrumented Application from developer or other who can run rtwBuildXcode.sh on a Mac and who has the source code for Application. [RmotXXXXXXXX.zip file]
2) Use RTWec "Add Application to list..." button and brows to the zip to "import" it into RTWec.
3) UnZip the zip and use iTunes (for Windows) "Add File to Library..." menu to navigate in zip folder to the instrumented iOS Device application [XXXXXXXX.ipa in “instrumented/iOS Device” folder]
4) Plug in iDevice to Windows using USB, select the App, click associated "Install" button, then "Sync" iTunes.
5) Now test as usual...
Thanks
MTWW in Worklight 6.1.0.0 and 6.1.0.1 (to be released, soon) does not support iOS 7.1.
Work is under way to provide support in a future release of Worklight.
I don't know what has happened to my Xcode, but since I deleted my app from the device, and tried to rerun it on my iPhone, I get this message coming from the top of the screen:
No such file or directory (/Users/spazm/Library/Developer/Xcode/DerivedData/newProject-cfjhjgezzcapwoadaivpptyywptu/Build/Products/Debug-iphoneos/proj.app/proj)
In addition, where you can select the "active scheme" (iPhone / iPhone Simulator / iPad Simulator), I used to have "iOS device", and right after plugging my device in, I would get my phone's name and everything would go sweet.
Now, I only see "iOS device" (after plugging in), and I need to select my phone manually, which seems like something went wrong here. I am not sure what.
In the xcode organizer delete "derived data"
Alternatively you can open "~/Library/Developer/Xcode/DerivedData" folder and delete derived data folders associated with your application. You also should make a clean/build.
For the second problem, again in the organizer window under devices find your device and click "use for development"
Edit: Today I have experienced again, deleting derived data did not solved the error this time. After deleting data, making a clean build, deleting the app from my device, I needed to close & reopen xcode, which finally fixed the error.
The problem was in the project file itself. Used my backup to load the old project, then manually added all the files from the bad-new-project.
Must have been some setting.
Try checking the Deployment Target for the app. I was getting this same error when trying to deploy an app that required iOS 6.0 to a device that had 5.1 installed.
Application get fail to launch in device having iOS 6.0 from xcode 4.5. Xcode says Application can't be launched timed out waiting for app to launch. I reset my all device settings. Cross checked if i choosed right provisioning. Yes, its right. here i am attaching image of console. Please help me out.
None of the above tips helped me. It turned out I was using my Distribution Profile instead of the Developer Profile in Debug mode. You can check the Profile you are using by going to
Build Settings->Code Signing Entity.
Make sure you are using your Developer Profile in Beta and Debug mode.
I had a similar issue when trying to debug an App with Ad-Hoc provisioning... Check which provisioning you're using, it seems ad-hoc provisioning cannot be used for debbuging.
Whenever this happens to me, I have done the following to fix the problem:
Stop the app from running in Xcode.
Delete the app from the device (or Simulator).
Select Product > Clean from the Xcode menu.
Close Xcode.
Close the Simulator (or restart the device).
Restart your computer (yes I know this like a Windows solution but seriously).
Try again.