I have issues after last update of BixbyStudio to version 6.10.0-r19i.8185 after submission as public or private:
When using simuator (or device) Im getting an error message: Missing a mock for Installed Apps. Add "appId": "com.samsung.android.bixby.service" and "appVersion": "1" to the apps.json file. For more info: https://bixbydevelopers.com/dev/docs/dev-guide/developers/ide.simulator#mock-installed-apps. When I go to this url there is no any inforation about this apps.json. Do you have information where I can put this file and can read more about it?
I have capsule with audio:
capsule {
id (my.app)
version (0.4.0)
format (3)
targets {
target (bixby-mobile-en-US)
}
capsule-imports {
import (bixby.audioPlayer) {
version (0.3.1)
as (audioPlayer)
}
}
}
which generates from that BixbyStudio for me deprecation warning
import '0.3.1-bixby.audioPlayer' does not declare itself as 'library' and will not be importable in the future, but im using same version from that document https://bixbydevelopers.com/dev/docs/sample-capsules/samples/audio
Please explain what is wrong here
Thanks a lot for your answers!
Support for testing audio library in Simulator is not available yet. However, you should be able to test the same on an actual device.
The next iteration of Simulator is expected to support audio.bixbyPlayer in a couple of weeks from now.
Re: import '0.3.1-bixby.audioPlayer' does not declare itself as 'library' and will not be importable in the future, you can ignore this warning for now.
Using audio player with simulator is a feature not yet available, but on-device testing should work. This new feature will be included in future release. However, I cannot confirm a definitive date.
No mocking in IDE is supported at the moment, this is a feature not yet available. There is NO way to invoke audio player or any other installed apps in simulator.
To confirm the audio player feature is working correctly on device. Please download example.meow and do private submission (you may need to change namespace) on your device. This is a large repository, the example.meow capsule is in subfolder audio. After confirming example.meow is working correctly, you can follow the syntax as an example in your capsule.
Good news! With the new 19I release and version (0.3.2), we finally got rid of the warning. And so is many other library capsules, please update your IDE and use the new version published here.
I'm also seeing this error also and can't find any information about where this file should be placed.
Missing a mock for Installed Apps. Add "appId": "com.samsung.android.bixby.service" and "appVersion": "1" to the apps.json file.
Related
Warning! I am beginner.
Apple testflight is refusing to accept any builds of a previously healthy project, sending out this message;
*
TMS-90809: Deprecated API Usage - New apps that use UIWebView are no
longer accepted. Instead, use WKWebView for improved security and
reliability. Learn more
OK, I understand that the UIWebView is now fully deprecated and no longer allowed.
I have scoured all the files in may app manually using the Xcode editor and find there is no reference to the deprecated string ( UIWebView ) in any file that I can edit.
Using the Xcode "find in project" tool also says it's not there.
If I build & archive, then run grep in CLI to examine the resulting package contents, the report is that the string "UIWebView" IS found in the app and the dSYM file.
Also, again using grep, I have examined the various framework files referenced in the editor, the report is that framework 'UIKIT' contains many references to UIWebView. The check does not reveal any other references to the string.
UIKIT is still shown as required in the build list.
I have cleaned the project, deleted all derived data, closed and opened the project and xcode.
Could any kind soul point me in the right direction here - I am stumped.
Thanks, Max
After learning a lot more, I found it was the PayPal external framework which had deprecated references in it. They no longer maintain it. I had to remove that and I added Braintree instead which is kept updated.
I had failed to check the external frameworks when trying to sanitise the cause. There is no magic bullet here...I just had to plod through all the components.
This was mostly caused by my inexperience and failure to understand the function of the various components of an app.
I am developing a flutter app. I want to let the user select some sounds.
When selected, I want the app to play its mp3 file in the assets folder. I tried with AudioPlayer plugin but I haven't achieved to play local files...
I have been searching for awhile and I haven't found any good answer to my questions, furthermore, the posts were created 2 or 1 year ago, so maybe we need an updated answer.
I have found this post: How to play local mp3 file with audioplayer plugin in Flutter
but my project doesn't find this package import 'package:path_provider/path_provider.dart'; [THIS PART IS SOLVED]
And when flutter will have a built-in audio manager? Are they/you working on it?
Thanks in advance!
EDIT: Also, I would like to play different mp3 at the same time, with different volume. Is it possible?
That import directive you see tells Dart that a particular source file uses classes from a different source file. The package: prefix tells Dart that the imported file is part of an external dependency. So you need to tell your project that you have a dependency. This is done in the pubspec.yaml file.
Dart's pub dependency manager takes care of finding the right version of the dependency for you, and downloading it. Add the path_provider package to your pubspec.yaml file. Each package's installing tab shows how to do this.
You can find a whole library of useful flutter (and Dart) packages here.
path_provider is a special type of package called a plugin which contains some Dart code together with iOS and Android specific code. This is necessary because playing audio or creating local files is platform specific.
EngagementReachAgent.Initialize(); does not exist in the current context
How can I solve this error? I can't deliver push notifications and I can't find anywhere a fix for this error. I tried everything that is explained here: https://azure.microsoft.com/en-us/documentation/articles/mobile-engagement-unity-android-get-started/
You did not follow the instruction well. You need to download and import the Azure Plugin package into Unity. You can get that here. When this is done, the EngagementReachAgent class and the Initialize() function will be present in your Unity project. They are not there now, so you can't use them.
Our NoFlo graph components have suddenly compressed themselves all into one uneditable box that says "WaitForward". See attached image.
For a while, this was happening on every browser, except Opera, so I could go in there and update graphs. Then, a couple of weeks later, even Opera wouldn't render the components, so now I am unable to add anymore logic to existing NoFlo forms.
We barely touch code related to NoFlo, so I don't think anything changed in our environment. My theory is that browsers (such as Chrome, which used to be the one stable browser to use for editing) have been updated recently, and this tool needs some kind of an update in order to render properly. Yet I can find no reference to this issue on the NoFlo GitHub instructions, and it doesn't look like anyone is having that issue here on StackOverflow (until now, of course).
The error message in the console says::
"TypeError: this.node.getTransformToElement is not a function"
I plunked this error into Google and saw that others are experiencing this with something called clientIO, and that recent updates to Google Chrome are to blame, as Chrome has recently removed a core feature that allowed related js to function.
But ... how can I fix this? That is the question!
It looks like recent updates to Google Chrome are the culprit.
Taken straight from jointjs.com's website::
Link to announcement from jointjs.com
Announcement: getTransformToElement() polyfill Nov 12th, 2015
Unfortunately, a new version of Chrome (48) removes a feature that is core to JointJS/Rappid. This feature is the SVGGraphicsElement.getTransformToElement() function. The motivation behind removing the method is - according to the Chrome team - open issues about how this method is supposed to behave.
To overcome compatibility issues with future versions of Chrome, we prepared a polyfill that makes sure this method exists. Before a new version of JointJS/Rappid is released (or if you, for any reason, don't want to upgrade), include the following code before you load your application JavaScript:
SVGElement.prototype.getTransformToElement = SVGElement.prototype.getTransformToElement || function(toElement) {
return toElement.getScreenCTM().inverse().multiply(this.getScreenCTM());
};
I was unsure exactly where to put this code in my noflo directory. So I tried putting it at the tippy top of the "app/js/main.js" file. It seems to be working! (But advice for a better location is more than welcome.)
I hope this helps anyone else out there who is experiencing the same issue.
I am experimenting with ServiceStack's JSON engine. I grabbed the MonoTouch binary build, v2.20. Works fine from simulator, but from the iOS device (iPad2, iOS5) I get an exception thrown by the type initializer for JsonWriter (and not much other than that). I am using MonoTouch 5, MonoDevelop 2.8.1, and targeting iOS 5. I have disabled library linking because I am getting an error when enabled.
I created a sample and uploaded to https://github.com/t9mike/ServiceStack-JSON1.
I'm trying to determine whether the issue is my compilation options, Service Stack, or MonoTouch. Thanks in advance.
A quick partial answer that might help:
I have disabled library linking because I am getting an error when enabled.
The current (5.0) managed linker can eliminate some unused (from a static analysis point of view) code from your application. This generally occurs when using Link all option, i.e. where user code gets processed by the linker.
One alternative is using the Link SDK assemblies only that won't touch the user code (only the code shipped with MonoTouch itself will be processed by the linker).
Another alternative is adding [Preserve] attributes on your code to ensure the serializer requirements are still met after the linker has processed your code. More information about the linker and [Preserve] attributes can be found here.
The next (5.2) release of MonoTouch will include a bit more sophisticated step in the linker to ensure the basic XML serialization and DataContract requirements are not broken. Not sure if this will solve this specific case (ServiceStack JSON) but I'll have a look into it.
As for the rest of your question I'll try to build this myself and duplicate your issue.
I ended up grabbing the ServiceStack.Text sources from GitHub, version 3.0.3. I created a new MonoTouch library project. I had to tweak ServiceStack.Text/JsConfig.cs slightly to conditionalize away the System.Drawing.Color bits. I'll send a patch and MT csproj to the authors.
After using this new assembly, my sample MT app ran fine on the device. I have updated my sample at https://github.com/t9mike/ServiceStack-JSON1 with the new ServiceStack.Text dll.