App inventor stuck at downloading

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. I'm trying to test an app with multiple screens but it's not working correctly. If this is a problem for you due to wifi or other issues, follow these instructions: Download the free app called ES File Explorer from the Google Play Store on your Android device. Use the App Inventor Designer Window to download the app to your computer. Your Blocks Editor Window must be launched to package your app successfully.

Using your computer, navigate to your file manager, find your device, and double click to navigate to its Download Folder. This looks correct? The product line uses this as its licensing mechanism. Prior versions use a different mechanism. I believe I installed the licence update via the desktop app mid day yesterday so I imagine that is what 9.

There's your issue.. The installation is trying to put the original licensing release back on but its been upgraded.. Right mouse click on the uninstall.

Have there been a lot of issues with this new licencing setup? The entire product line depends on this new licensing mechanism.. For some, no problems, others the service will not install. And others the service will not even start.. Its the name same for each end user or machine. Subscription, Installation and Licensing. Share your knowledge, ask questions, and explore popular Download, Installation, and Licensing topics.

Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.

Back to Subscription, Installation and Licensing Category. Back to Topic Listing Previous Next. Filter by Lables. Message 1 of Inventor installer hangs. Run CCleaner to uninstall any traces of Autodesk installs and repair registry. Redownloadd the installer. Repair registry again and reboot. Message 2 of Message 3 of How are you downloading them for installation? If your computer has a firewall, check to see whether it is turned on, and, if so, which ports and applications it is blocking.

It might also be the case that some other program running on your computer has grabbed the port that App Inventor uses to talk to the phone, generally port Try to check that. If you are using one of the more recent versions of the Android operating system, version 4. Look here for some background. App Inventor should now work. Still having issues? Check out the google forums for more help and advice. Here is a forum already on this topic. Try the following steps to troubleshoot your wireless connection.

If you have a "telnet" program you can attempt to telnet from the computer to the phone on these ports. If the connection won't complete, then there is likely a firewall in place that is blocking connections to the phone. Directly loading App Inventor in this way means that the Play Store can not automatically update the App. When there is an App Inventor upgrade, you will need to manually update the Companion App.

If you attempt to use an older version of the Companion App with App Inventor, you will be prompted to update it. I followed all the wireless instructions and my phone is connected to wifi, and I still cannot connect to App Inventor via wifi. If you have trouble connecting using these wireless instructions, make sure your phone is using WiFi and not the cell network. On some devices and in some locations, even with WiFi enabled, the phone continues to use the cell network for Internet connectivity.

If this is happening to you, you can disable mobile networking cell phone carrier based Internet connectivity from your device's Android settings menu. There's a permissions issue on shared Macs in that results in the first person to log in being able to use the emulator, but subsequent people cannot. You'll have to do this each time a new person logs in.

If that doesn't work, unplugging and reconnecting the phone to continue work, but there can be all sorts of reasons for this. Ask for help from other users in the App Inventor Forum. First try clicking the button in the Blocks Editor that says either "Connect to Phone" or "Restart Phone App" the button will be labelled with one or the other. If that doesn't work, try unplugging and plugging it back in.

Followed by clicking on the "Connect to Device" button. Finally, please try closing and restarting the Blocks Editor. I was developing an app and I unplugged the phone, and the app disappeared from the phone. It's supposed to disappear. If you want to use the app when the phone is disconnected, you'll need to package it and download it to the phone.

If you are developing, and the phone accidentally becomes disconnected, you can continue work by plugging the phone back in and pressing "Connect to Phone" in the Blocks Editor. Once the phone reconnects, your app should appear again.

The code size for the apps I create is very large. Even the simplest apps have apk files that are larger than a Megabyte. There is a known issue with certain virus protection software, in particular the "Dr. Web" anti-virus app. Any app that uses the texting component SMS will generate the virus warning "android. This is a false positive virus detection that you can safely ignore.

Apps with multiple screens must be packaged and sent to the phone to test. 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 same things as with images, above.

Watch out for running out of storage. See Media for information on media in App Inventor. And make sure the audio file is a format the Android and hence App Inventor knows about. This error occurs if packaging 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 might be bad names for figures or other assets, that can trip up the compiler.

If your project gets this error, think about whether there could be causes 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.

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. What is a keystore and why might I want to upload or download one? 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.