I am getting nuts a little bit.
I am working on SoundJS app for an alarm. The user will share a link and when somebody click on it, after the user defined time the alarm will sound.
I have this link:
http://online-timer.en.downloadastro.com/tools/?PageSpeed=off#5000
I am using SoundJS 0.6.2 (which should be the latest)
But the alarm not working in iOS, it works perfectly in Android and PC. Works ok on my MacBook. but not on the iPhone.
Please advice
Well on GitHub and in Slack an answere was given.
This is an iOS limitation, and some of the Android have it too.
This issue is because I must "unlock" the web audio context on iOS using a mousedown/touchend event. In SoundJS 0.6.2, any document-level click/touchend will do it (so there is nothing extra that is need to be done). Earlier versions required to do some additional manual steps (which can still be seen in the MobileSafe demo in GitHub, which is not necessary any more).
Related
My app Plumb-Bob is based on the IKImageViewDemo:
https://developer.apple.com/library/archive/samplecode/IKImageViewDemo/Introduction/Intro.html#//apple_ref/doc/uid/DTS10004049
I compile it for MacOS 10.10+ and in my tests I noticed that the "move tool" is not working at all in Mojave (10.14) while it does as usual in the previous systems.
Since I have strongly modified IKImageViewDemo for my purposes, I have downloaded it again to make some test (see link above).
When build and run IKImageViewDemo I have verified that it has the same behavior:
On MacOS 10.14 the move tool shows its open hand cursor, but, when dragging, the image is not moved at all.
On older MacOS, it works like a charm.
I did not find any updates, deprecations and changes on IKImageView framework in 10.14, searching at Apple Developer's docs.
Can anyone address me to the solution, it is very important, in my app, to move around the zoomed image.
Thank you in advance
I'm having a real difficult time setting up React Native on Visual Studio Code on my mac. I have read multiple tutorials and watched youtube and Lynda videos on how to do it - follow the steps exactly as they are presented, but still it doesn't completely works. It seems like every other terminal command I run gets an error.
I have managed to get it running on my physical iPhone and in the Android emulator. But when I try get it up and running on my iOS simulator using the appropriate terminal command, it won't work. The simulator opens, but then the terminal seems to get stuck loading and the app isn't showing in the simulator. There's no error, but it doesn't run.
Another thing is that I don't seem to find the index.ios and index.android files respectively - just a single App.js file.
I guess what I'm asking for is a good thorough guid on setting it up. Most guides I come across seem to leave out or under-explain certain steps, assuming that you already understand certain concepts. Please post a link if you know any super guides :) Thanks!
I'm trying to run an app made on Titanium in my cellphone. At first it was working fine, until i decided to debug my code. After that whenever i try to run it on my cellphone, it gets stuck # the powered by titanium screen (that red one).
I tried to delete my build folder as some people said after a bit o research but it won't work.
How can i solve this?
What I would try to do is:
clean the project (it also deletes the build folder, but I think it also cleans some more stuff in there).
when the app starts try to set an alert in app.js as the first thing - see if this alert shows, and if it does - move it to the next step until you find a place where it is no longer shown which might indicate that this is where you problem is.
Look at the device logs - if it's an android device open ddms and look at the logs while you run the app - see if anything pops up. If it's an iPhone on xCode you have some sort of console viewer for the phone (sorry - can't remember the name right now).
make sure you are not still running under debug mode.
BTW - you didn't mention if it happens on iPhone or Android? does it happens on the simulator as well?
I was having the same issue. From digging through Appcelerator's Jira I found we weren't alone, and also got a workaround that allows us to get past the splash screen. Check to see if there is a deploy.json file located in your application's directory on the device. If so delete it!
Here is more info on the issue https://jira.appcelerator.org/browse/TIMOB-16086.
It's rated as a high priority to be corrected for the 3.3.0 SDK release.
I've installed Testflight (1.2 B3) as stated in the documentation. Builds are uploading and updating fine. I can see sessions (mostly anonymous :/), I receive the logs (TFLog) - but I do not receive any crash reports. I even introduced a crash-on-event (a method not found thing) - but theres is nothing on Testflight about it.
Provisioning is via a developer profile which embeds several devices.
The problem occurs on iOS6 and iOS5 / iPhone5 and iPad3. The is being build against iOS6.
Any ideas?
UPDATE
I've tested several other frameworks and ways to receive crash reports. Nothing worked so I suspect something in my code (obviously). Are there any other switches that XCode 4.5.1 might have enabled and that way disable any error reporting during a "production environment" like setup?
UPDATE 2
As of now we're using Testflight only for distribution of beta versions and switched to Crashlytics for crash reporting. It's a bit more streamlined and fetches most crashes.
I also do not get any crash reports via TestFlight. This is what the TestFlight people told me:
Our team is currently looking into an issue associated with auto
versioning of the app when uploaded and SDK data not reporting
properly. Looking at the URL you provided it looks like the build
version is not changing before uploading the app to TestFlight and our
auto versioning implementation is causing an issue with general SDK
data reporting.
I will share this with our team and we will contact you when we have
an update available.
I tried to update the build version to avoid auto-versioning, but it did not help me. But maybe this issue is hitting someone else.
Testflight did not satisfy our needs to log crashes. That is why we skipped to Crashlytics (as I said in the original post). The issues with Testflight seem not to be resolved. We still do use it for distribution, that is what it's good at.
I just started doing some research into Core Location and it seems that the tutorials that I am following are not working for me. Even when I download the source code and run it, nothing happens. At present I have attempted this tutorial. When I run it, I get a popup asking if I want iPhone to use my current location. I press ok, and then nothing happens. Am I supposed to do anything else?
I am also using VMWare, and currently am unsure if this is the cause (although my internet connection works perfectly on it). I'm using base sdk ios 4.3 - running simulator.
In order for location to work, you need to be running the code on an actual device. The latest public iOS SDKs don't yet support location changes in the simulator. The simulator will always return 1 Infinite Loop, Cupertino, CA (Apple's headquarters) as the location.
See the Core Location documentation for more information on using location in your apps. (Although I can't find a citation for the limitation of the simulator at the moment.)
CoreLocation within the simulator is always going to return 1, Infinite Loop, Cupertino, CA, although Xcode 4.1 and iOS 5 have improved support for testing CoreLocation capabilities in the simulator.
iOS5 iPhone simulator supports location simulation.
If you are using 4.3, it does support location in some conditions. I notice that when I am tethering using my iPhone, my iPhone simulator is able to get location from my phone. I can see location update in my simulator when I'm working while commuting in a train. But this update is only through core location. Map gives u Cupertino unless u use iOS5