I have ported my ios game to android using indie version. It has following issues:
Custom scroll implemented through code doesn't show up
Touches on ccmenu works on and off i.e i have to restart the game again and again sometimes they work sometimes they don't.
Nib files have the same issue mentioned in step two. Works on and off have to restart again and again.
Game icon is not appearing
Sometimes game stucks randomly and crashes.
Update:
Note: UIScroll works where we have used them in tableView and doesn't work where we have only used UIscroll.
Related
Since I upgraded my Android Studio installation to Bumblebee, the emulator has become unusable. It either crashes during startup or gets itself stuck so that the UI is unresponsive and the debugger either cannot install or cannot launch an app. The way in which it fails varies from time to time for no reason that I can understand. although different virtual devices seem to behave differently. I tried deleting my old virtual devices and creating new ones, but that didn't help.
I can't debug my code on a real phone because of a different problem, see my recent answer to Source code does not match the bytecode for Android's View.java.
When it crashes I send a crash report to Google, but they don't seem to be fixing it. The problems started with the first official Bumblebee release 2021.1.1, which seemed to have a complete new version of the emulator, and I'm now on the latest stable version 2021.1.1 Patch 2.
My environment is a Dell Precision M4800 with 16GB of RAM and an 8-core Intel processor, using an external 4K monitor and an external full-size keyboard, running Linux openSUSE Leap 15.3 with all recommended patches installed.
Does anyone have any suggestion short of throwing away my entire Android Studio installation and reverting back to Arctic Fox? Has anyone else seen similar problems?
Tintin's answer didn't work for me: Device Frame wasn't enabled anyway because I had noticed that it had caused problems before.
However the following sequence rather surprisingly, at least to me, did fix the problem.
First make sure that the toolbar is visible at the top of the emulator window: if it isn't, click on the gear settings icon at the top right of the emulator window and enable Show Toolbar.
Start up an emulated virtual device, and before it crashes click on the three dots at the right hand end of the toolbar: this will bring up the extended controls window.
Choose Settings from the list at the left of the extended controls list.
Set the OpenGL ES renderer to Desktop native OpenGL, and the OpenGL ES API to Compatibility (OpenGL ES 1.1/2.0).
Close the extended controls window and then close the Android Emulator window.
Check if there are any zombie emulator or qemu processes still running. If there are, kill them: you'll need kill -9 on Linux.
Try to cold boot an emulated virtual device: it will probably crash before it even gets started up properly.
Close the Android Emulator window and repeat step 6
Try to cold boot an emulated virtual device again, but click on the three dots quickly before it crashes.
When the extended controls list comes up, choose Settings from the list at the left.
Set the OpenGL ES renderer back to SwiftShader, and the OpenGL ES API back to Renderer maximum (up to OpenGL ES 3.1).
Repeat steps 5 and 6.
Now try to boot up an emulated virtual device again. It should work: at least it does for me.
If it doesn't work on your configuration, try all possible combinations of the OpenGL ES settings: you may find one that works.
Logically, changing the OpenGL ES settings and then changing them back again shouldn't do anything, but it does. My guess is that perhaps some needed bit of initialisation for the OpenGL isn't being done by the installer, but it gets done when you change the configuration.
I also faced this problem in both updates in 2021.1.1 it was not working at all. Updated to patch 2 again faced problems turned off Enabled Device Frame it is working OK now
I am new to react-native, I worked with different work-arounds but got fail nothing gone to work, when I use react native camera in my application it perfectly works on Android device or simulator but when it comes to IOS application crashes, many posts said that is because of info.plist and I added the permissions there as well by going to: ios/myproject/info.plist via myproject.xcworkspace I added the below information, the permissions works correctly when I allow my application by pressing OK it suddenly crashes with no error and when I try to reopen it, it is not able to open on IOS, simulator as well as on device.
In some examples I got the text on the screen Camera is not Authorized, while some crashes it thoroughly.
note: when it take permissions from me and I allow the permissions the application crashes in IOS only, and in some cases it gives a string on the screen by saying "camera is not authorised".
I hope somebody help me
This is the info.plist
set my paths as in the pod file:
I'm using the new Android Studio 2.0 (Beta 6) and I'm facing a serious problem. After updating, I noticed that there were some problems with the Instant Run feature, where it was quite hard to ensure that the application was actually running new code. I disabled the Instant Run feature immediately.
Despite this, I am noticing that Android Studio does not always deploy new code anyway!
I have tested my theory by adding a print when my Activity is created and it doesn't get called. If I close the application (for example by pressing the back button) and then running the code - it works as expected.
I have also verified that it's actually a problem, since old code is run after pressing the run button.
What the F is going on and does anyone know a fix? (Except reinstalling AS 1.5)
Notes and summary:
There is no lightning bolt on the Run Button
Activity onCreate Print is not called after pressing run
Changed code is not updated after pressing run
Instant Run is turned off in Preferences (And restart activities on code change is on)
It doesn't happen every time - roughly 50 % of runs
I wanted to develop my own watchface for my Gear S2. I found some good documentation on downloading and using the Tizen IDE. All is well, but I'm finding the tweak css/html5-run/upload-switch faces-view-wash-rinse-repeat to be very tedious and time-consuming.
I know I can point my browser (Chrome) to my development workspace and load the index.html up and I surmise that I could tweak what I have, which came from the template to work in the browser if I made the sizes in the css static vs dynamic (absolute vs percentages). But is there a better way? Scouring the Internets Googles have yielded nothing too helpful yet.
moderators: this might be OT for this particular SO. If that's the case, I apologize. A nudge in the right direction would be greatly appreciated, if so.
So, I was able to make a little progress on this myself. I am using Chrome in developer mode, which almost works perfectly when using the developer device emulator. To toggle the device emulator, open developer mode (windows: ctrl+shift+I, OS X: cmd+option+i) and when the tool window opens up, look for the little device button next to the element button in the upper left corner of the developer tools window. When the device emulator open, switch the resolution to 320x320 (top of the window next to "screen").
Now, open your index.html file for your project in Chrome, and you can at least muck around with your css styling.
Now to get around the whole issue of reloading your clock with the default clock in the Java emulator for Tizen, I was able to get my changes to automatically assert when running the new code. The way I did it, though I'm not sure if all of these steps were necessary was:
In the emulated watch:
1. set the screen timeout to 15 mins.
2. set the watch face to your development watch face
In the IDE:
1. when ready, use the button for smart launch (it's the blue button just to the left of the bug button in the tizen web IDE). This is in the Tizen SDK version 2.3.1 build 20150721-1440.
At the time of running your code -- making sure both your emulated watch is running too:
1. In the IDE, click the smart launch button
2. Click over to your emulated watch and make sure it's in focus.
It should update the watch face with your latest changes in realtime. This worked for me, so YMMV, but at least I didn't have to reload the watch face after asserting the latest version.
I created (in Qt5 under Linux) a small QMainWindow app.
I noticed that when I'm clicking on the minimizing button, I cannot see my app anymore. In other term, I cannot see it in the bar !?
I tried with docky, cairo-dock and native Mint bar and... nothing work !)
Any idea ?
Is this running it in the debug mode inside of Qt Creator? Maybe you have to deploy it and run it outside of Qt Creator for it to get its own button on the dock/taskbar.
If not, you might have a bug that should be reported to qt.