unity 5.4 apk installed but won't open - unity3d

Okay, so basically I build my game in unity, saved it in a folder and drag the file in a folder on my phone, made sure unknown source was checked and installed it on my phone.
However when I open it it shows the unity splash page but then it closes for some reason I do not know, I searched it up tried all different resources but nothing worked, it still did the same thing, I tried it out on my brother's mobile and it worked fine for him (it didn't close and it let him play my game).
It just doesn't work on mine. I'm using unity 5.4
Can anyone help me with this problem?
Okay problem has returned agian
Thank you. :)

Try to uninstall all the previous version of the app from your Phone and then try to re-install it.
If the above plan didn't work, Change the build settings in Unity from Prefer External to Automatic,
I hope this will help you...

my problem got resolved by deleting the android manifest file and then building again.
I hope this will help for people like me in future.
P.S : for me manifest was located at plugins/android/androidmanifest.xml

Related

Unity3d crashes when trying to change platform or building after upgrading to win10

http://prntscr.com/cfakce this is what happened when I'm entering any script, when I'm changing to mobile input this show up http://prntscr.com/cfalpw.
Whenever I'm trying to build the project or changing platform it crashes.
I changed my win7 to win10 (had to) and I think it may screwed my project but I'm not really sure, tried to search on Google for those errors and found nothing.
Someone told me on the Unity forum that it had something to do with UnityEditor but didn't had really idea how to fix it.
When I had win7 (before the change) everything worked perfectly fine.
Any ideas?
Unity version: Unity 5.4.0f3 (64-bit) thought it might help.
new: When I'm writing using at the start of any script it doesn't complete it to Unity.Engine or Unity.Editor it doesn't even have this option, like it got deleted or something. How do I bring back those Unity.editor and engine? I think it's the real problem :)
Another thing is that when I got win10 the C drive is now F and I've got new SSD drive which is the new C, everything stayed on the C drive but they didn't work or was used perfectly, so I redownloaded everything like Skype, steam, Origin and of course UNITY, the project folder I dragged to my desktop and then opened the game folder on this Unity I downloaded, I think that's what made the problem because when i enter Unity and press open, and going back to F drive>users>myname>dekstop>UNITY>mygame and open it in that path instead of what i have dragged (which it the same folder but on different place) it let me switch platform, does not let me build but at least it's not crashing just giving me the same errors without crashing, i don't know if this has something to do with but just gave the info cause maybe you will find this helpful to help me.

Unity updating licence takes a long time and doesn't start?

I got Unity 5.3.0 from the Unity official website ,I installed it,
while running it ,I Signed-in using my Username but it gets stuck in the "Updating License" Window
can anyone help me with that ?!
thanks in advance
It happened for me twice for now. As Sean Powell was saying, you should close and reopen the application few minutes later. I think it's a problem with the license server connection.
Have you tried uninstalling and reinstalling? or restarting the application?
I had this problem too. Don't waste your time with unistall-reinstall. Close Unity, delete Unity_v(your unity version).ulf file in "C:/ProgramData/Unity", and reopen Unity. This should solve your problem.

Unity crashes on my PC and I don't know why

I was doing a course for learning the platform Unity and how I can make video games, etc..
I have installed the program in my PC, and the installation was correct, but at the time for starting the program, it doesn't end to start and windows told me, "The program stopped working, close it" and always the same.
Someone knows how can i fix it?
Thanks in advance
Try re-installing, checking you've got the latest version and you meet the software's requirements. A printscreen would also help.
Hold down the Alt key and click unity.exe this should let you open or create a new project rather than try loading the one that is crashing.

iOS:Fetch all gmail Contacts into your iOS app

I have gone through gdata-objectivec-client but i am not getting any way to include
gdata api(framework) into my iPhone app as Gdata.framework file is in red color means missing in downloaded source code
I have also downloaded sample code(http://gdata-objectivec-client.googlecode.com/svn/trunk/) but none of them is running on simulator
Please help me with any Tutorial or sample code
Thanks in advance
Hi Dinesh I'm not sure whether u have solved your problem or not but to overcome from this issue what you can do is open the Xcode Home window select the second option named Connect to repository and paste the link into Location then click on checkout. Select the destination where you want to import it. And you are done.
It worked pretty well for me. Hope it helps

Xcode 4 not launching application?

Today, after installing Xcode 4 with the 4.3 SDK, I attempted to launch my application. However, the application will build and the iOS Simulator will pop up, but I get a message in the window in Xcode that says "Attaching to YourApp" which stays there indefinitely. How can this problem be fixed?
I had the same problem, that is, when I launched my application in the simulator, Xcode was hung waiting for the simulator to start. The simulator showed a black screen - nothing at all.
Note this is a project that ran fine on Xcode 3 and is the exact set of files used to build the application that is currently for sale at the App Store.
Okay, so here's the underlying problem, and my solution:
My application name was "ultimateTimer.app", as seen in Xcode under the Products folder. However, this was NOT the name in the project file.
Here's how to found out:
Click on your project in Xcode (it's usually at the top, e.g. mine is called ultimateTimer.xcodeproj). Under "Build Settings" tab, look for the "Packaging" area and specifically for the "Product Name" variable. Under Product Name, I had three entries:
Debug
Distribution
Release
Under Debug, it had the value "TalkUltimateTimer" which was an old name of mine. When I changed this to "ultimateTimer" to match the "ultimateTimer.app" as above, I found the Xcode attached to the simulator correctly.
This happened for me for iPhone applications. I opened the simulator myself and switched the device to iPhone Retina Display and from then on it worked. I tried switching back, but it didn't work again, so I have had to keep it on the Retina Display simulator, and if I need to test non-Retina Display I'll use the iPad simulator.
I skimmed the post and these seem to be the two solutions thus far:
I think I figured out the problem:
I went to 'Edit Schemes', and for some reason, the scheme I was using was pointing at BumpDev.app as the executable instead of bumpdev.app. Changing this made things work. Perhaps there is an issue when converting from xc3 proj files?
Anyways, the app now boots in the simulator. Yay!
And the other solution in that post is:
Did your project by any chance have a folder reference with images in it?
For me the problem only happens when I have a folder reference in the project. When I remove the folder reference and instead add the folder as a group, clean the project, and hit launch things work fine. In the "Copy to Bundle" phase each image is then listed individually, whereas when I had a folder reference, the whole folder was listed.
This took me a really long time to figure out. It was quite frustrating, but I'm glad I have a workaround until the bug is fixed.
I had the same problem after swapping the mouse for a new one. restarting my iMac resolved the issue.
I just upgraded to Xcode 4.3.2 and had the same issue with new projects. After poking around and comparing projects, I found out that new projects were set to the LLDB dbugger and the projects that worked were using GDB.
After changing the debugger for the new project to GDB, it worked. I am yet to research what the differences are, but at least I can now run my new projects.
Ensure you are starting a proper scheme.
I. e. when using CocoaPods, running Pods scheme would not start emulator.
It's a known issue. Have a look at this thread in the official forum.
Hey, update Xcode to 4.0.2. Problem solved :)
I had the same problem, I tried every solution here, but no works. Finally, after I rebooted my computer, the problem was gone.
Restarting the simulator worked for me