I am working on a Instagram face filter/effect with SparkAR. It is successfully uploaded, approved and works just fine when across many devices when I try the effect in the Instagram app. I can select the effect when creating a Story however – I cannot when doing a Live stream. The effect symbol doesn’t show up nor can I select it when searching for the effect, while all the other effects are still there.
One user reported that she was able to select the effect during Live on her Android device. But at least on iOS devices it seems to be impossible to find or select the effect.
Are there any differences between Live and Non-Live effects? Or between iOS and Android effects? Has anyone had the same problem before? How can I make sure that my effect is available for Live streaming?
Thank you for any hints!
Turns out, that the use of audio inside the filter caused it to not appear in Live mode.
I removed all audio files and playback controllers and enabled the microphone. It now works.
I've encountered a problem today when testing my Android app with different emulator settings.
Upon clicking a button a certain amount of data (~161kb) is fetched from an online XML-Document.
Up to now I tested the app with full internet speed and faced no problems when fetching the required data. Same for LTE. However when testing with HSDPA and lower mobile radio standards the data wont get loaded.
The data is fetched from an async background task and the fact that it works with LTE makes me believe the code is doing what it should. Furthemore the amount of data is marginal with ~160kb.
My question: Could this problem be caused by the emulator? If so, how could i resolve it?
I am trying to price out various azure services and when I add them to the calculator and make changes the estimate does not update.
I have tried this in Edge, IE, Chrome, Firefox (normal browsing and Private) and I get the same results.
I also ran CCleaner and removed all of the files for each browser.
The calculator did work a few days ago.
Any ideas?
I had the same problem. A solution that works for me is to open a new InPrivate window from the Edge browser. (A new private window from Firefox did not solve the problem).
Perhaps the problem is related to cookies? I have not tested after deleting all cookies. #jake, when you used CCleaner, was it set to delete cookies or just cached data and files?
(For what it is worth, in the Firefox developer console I see several warnings related to failed loading of JS scripts. I can't say if such a failure is the cause of the problem, but it looks like Microsoft needs to do better testing of the calculator page.)
I´m planning to make a full dynamic site using pjax, with static menu (only the content will be updated with pjax). How bad is this?
The site that i have planned to implat this on have a lots of data on it, most images.
I have tested my solution on my local machine and it seems to work but in production it will probably be slow or what do you guys think? Are this bad practise?
Now on pjax start i slide out my container to the left, and slide in the new content from the right. I have noticed a small performance lost when i do this in Safari and FireFox. Should i skip my solution and just do regular updates of the page? I want to do something like Twitters iPhone app, but on the web.
The reason i want to do this are that i have a full size google maps with a lot of pins that take some time to load.
I have found Tubrolinks (http://www.github.com/rails/turbolinks) that would be included in Rails 4.0, its great adn i think a good answer to my question.
I'm tyring to get phonegap up and running on blackberry storm (9530 simulator). I had been testing my webapp from withing BB's built in browser, and it was looking ok, but then it totally bit once I tried to look at the some code from within phonegap, even though I was pointing phonegap to the same url (I hadn't yet gotten to the point of running code locally on the device).
I tried a test case on google and got similiar results. see below. I suspect that I'm missing something basic here. I would have expect both images to be nearly identical.
Browser
http://www.eleganttechnologies.com/outside/ImgDeviceBB9530WebGoogle.jpg
Phonegap
http://www.eleganttechnologies.com/outside/ImgDeviceBB9530PgGoogle.jpg
[Update]
To shed some light on what is happening, I ran the browser and the embedded browser (phonegap) against the W3 mobile web acid test: http://www.w3.org/2008/06/mobile-test/
I definitely notice differences between the two, but I don't yet know the 'why' and the 'how-to-address'.
Acid via built-in browser
(source: eleganttechnologies.com)
BTW - I ran this earlier today and got a couple more green square than just now.
Acid via browser embedded into phonegap
http://www.eleganttechnologies.com/outside/ImgDeviceBb9530PgAcid.jpg
Disclaimer: I don't know anything about phonegap, but have a pretty good theory. By default the embedded browser control on BlackBerry uses an older version of the rendering engine than the BlackBerry browser itself does.
At the BlackBerry developer conference last year, a talk was given about this, and there's an undocumented option to use the newer rendering engine. \
The option ID is 17000 (yes, a magic number, which could change, use at your own risk etc), and should be set to true. Not sure how you'd pass this option through phonegap (I'm not familiar with the toolkit) but using the BlackBerry APIs it's something like:
BrowserContent content;
...
content.getRenderingOptions().setProperty(RenderingOptions.CORE_OPTIONS_GUID, 17000, true);
I don't know the specifics of the browsers you are using, but I do know that most of the big sites will detect your OS + browser combination to decide what HTML to show you.
If Google is seeing a different user agent, you might get a generic mobile version of the HTML instead os the Blackberry specific HTML you get for the built in browser.
If you have access to a web server, try hitting it with both browser setups and see if there is any difference in the log file. That might tell you something interesting.
As we can see in your Acid tests...
One browser (the built-in one) is reporting correctly as a BlackBerry9530, and the other (phonegap) is not presenting the user-agent ["Testing with ."].
In this case, Google is providing you with the default view of their homepage, whereas when you are reporting yourself as a BlackBerry device, you will get the BlackBerry specific rendering.
By the sounds of things, using phonegap is removing the default user-agent (most probably because it's not recognising your device). As phonegap is open-source, the best bet is to get in there, and debug it and find out what happens with the user-agent when the http requests leave the device and track it back from there.
Maybe one browser has capabilities that another one does not?
Hm. By looking at the screenshot I would say that the second page is probably missing some resources. It may be missing some images, scripts and the CSS files, which would explain different l&f. Knowing how Blackberry Browser Field API works, I would guess that the implementation that uses the BrowserField was not done correctly. Just my guess. In addition to that, when the browser field is initialized the caller needs to configure it properly by enabling the appropriate browser features - scripts, styles etc. Again, the API is done in a very weird way, I have gotten myself into this trap once. When setting the options, you cannot just create one mask (like CSS | WML | SCRIPT) and make one call. Options are numeric and, I believe, non-overlapping - but you still need to call the API for setting each option independently.
Also the way asynchronous loading of the resources for BrowserField takes time to understand.
Just my $0.02.