If this is a problem for you due to wifi or other issues, follow these instructions:. I set the image property of a button or other component to an image file, but nothing shows on the phone. I set the source property of a Sound or Player component, but there's no sound when I tell the phone to play. If you are working with the phone connected to the computer, make sure the phone really is connected.
Try using "Do it" on a few blocks, including the block that tells the component to play. Also make sure the phone's media volume is not turned down! If this doesn't help, try some of the same things as with images, above. Make sure you have enough storage. See information on media in App Inventor. And make sure the audio file is a format the Android and hence App Inventor knows about. First, check to make sure that the volume on your device is all the way up.
Also, be sure you've got something typed into the dark pink text block, and that it is plugged into the purple TextToSpeech. If that text box is blank then you aren't telling the device to say something. Then, if you still don't hear anything, check to make sure your device has Text-to-Speech installed. It is supposed to be standard on all Android devices. You should see Google Text-to-Speech. If it's not there you can most likely install it from the Google Play Store.
This error occurs if building the project fails at the very last stage. This error message is a catch-all that covers "unexpected" errors where App Inventor hasn't provided a useful error message.
There are several situations where this error has been observed. One is with large projects that have multiple screens: The individual screens build correctly, but the system runs out of space in putting all the screens together at the final packaging. Another situation is where the project file is corrupted, for example by the user unzipping it making an edit and then re-zipping it.
This can lead to spurious files being included in the new zip file, which confuse the compiler. Another issue might be bad names for figures or other assets, that can also trip up the compiler.
If your project gets this error, first check for issues like the two listed above. If that doesn't help, try asking in the Forum : You'll need to attach your project source so that someone can try to diagnose the problem.
This could be the result of a transient storage failure, so try again. If the problem persists, this could be a similar issue to "unexpected problems generating Yail," above. One program issue that causes a build failure is if your program contains two event handlers for the same event with the same component for example, two Button1 when-clicked definitions. This is a known bug in App Inventor that will be fixed.
Until then, if your program build fails, check to see if you've defined multiple event handlers for the same event. When I try to install my project on the phone, I get the error "unable to parse package". If you get this error message you most likely are trying to reinstall an app on your device that you have previously packaged and installed with a different App Inventor service. For example, you might have packaged the app originally with the Google App Inventor service and now you are trying to re-package with the MIT App Inventor service, or with a service that someone else is running.
If you don't have any data associated with the app on the device e. If you need to preserve the data associated with the app, and you have a copy of the keystore that was used to package the app that is already installed, see below for how to upload the old keystore to the new service. Every Android app ". App Inventor generally handles this for you behind the scenes, so that most users don't need to think about app signing most of the time. However, you might run into a situation where you need to know about app signing if you move between different App Inventor services and you want to reinstall an application that was built on a different service while still preserving its local data.
App Inventor keeps the key used to sign your apps in a file called a keystore. When you first start using an App Inventor service it creates a new keystore for you and uses that to sign any apps you package on the service.
If you move to a different App Inventor service and want to keep using the same keystore to sign your apps to avoid the inconsistent certificates problem mentioned above , you will need to download or otherwise obtain the keystore from the old service and upload that keystore into the new service.
Options for downloading and uploading keystores can be found in the My Projects tab, under the More Actions menu. Note that the same keystore is used to sign all of a user's projects in a given App Inventor service, so you cannot designate one keystore for some apps and a different keystore for other apps. How can I get the keystore that was used to package my apps in the original Google App Inventor service? Most users of the original Google App Inventor service can find a copy of their app source zip files, as well as the keystore that was used to package their apps, in their Google Docs accounts:.
I received the message "We detected errors while reading in your project" when starting App Inventor or Switching Projects. The copy of your project received by your computer differs from the version sent by the MIT App Inventor server. This is most likely caused by a server or filter, not controlled by MIT, located between our servers and your computer.
This is an especially unhelpful error message that will be fixed in the next update to App Inventor. It is generated when App Inventor cannot complete the compilation of a program. The most common cause for this is that there are two event handlers for the same event with the same component for example, two Button1 when-clicked definitions.
Check your program for this and try again. If that is not the problem ask for help in the forum, and include the name of your project. In the news Events Stories from the field. App Inventor Blog. Troubleshooting for App Inventor 2.
I'm using the emulator and it says that my Companion is out of date. I'm trying to use the emulator, and it's not working. My app runs on the emulator, but images do not appear. How do I update the App Inventor Setup software? App Inventor is telling me to restart the aiStarter program. What is that? More help with aiStarter On Windows, App Inventor cannot connect to the device, and the command window for aiStarter shows: The system cannot find the path specified.
My Blocks vanished from the Blocks Editor. The Blocks Editor won't connect to the phone or media files don't show up on the phone. I'm using wireless and the phone won't connect to the blocks editor. The Companion started to run, and then said "Connection error. I was using the emulator and now I can't use the USB cable.
I was developing an app and it crashed on the phone. My phone doesn't seem to match what's in my program. App Inventor apk files are in fact very large. We're working to reduce their size. My app causes a virus warning. Update: When I open Google Photos, go to 'Photos on device', and select 'Download', I can see all the deleted images the images that should be on that folder and it doesn't.
Check if you have storage manager enabled. It will automatically start deleting backed up photos and videos after they cross the selected timeline. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Android automatically deletes content of my Downloads folder Ask Question.
Asked 1 year, 11 months ago. Active 2 months ago. Viewed 3k times. Any clue where can I look? It's annoying Regards Update: When I open Google Photos, go to 'Photos on device', and select 'Download', I can see all the deleted images the images that should be on that folder and it doesn't.
Improve this question. Find recently deleted apps from your Android Phone. As soon as you see the deleted app, tap on it and then click on the Install option to get it back on your phone.
The Play Store will again download the app and install it on your device. It is the most simple and easy way to recover deleted apps. DroidKit is right here to help you recover APK files, with which you can easily get back your favorite apps. With no technical knowledge required, you can free download DroidKit on your computer and take the following instructions to see recently deleted apps and recover them with simple clicks. Step 1. Step 2. Step 3. Since rooting Android phone will erase its data, you should decide whether need to back up Android data in advance.
Step 4. Besides recovering apk. In this case, what you need is the professional Android data recovery tool — PhoneRescue for Android , which is one of the best Android data recovery tools that can help you find all lost apps data back with only a few clicks. You can check its main features below:. If you accidentally deleted apps on your Android phone, and need to get app data back, PhoneRescue for Android allows you to easily recover deleted app data with or without root. With so many advantages, you can download PhoneRescue for Android and check the simple steps below:.
0コメント