I had the chromecast working following the guide at https://developers.google.com/cast/docs/android_sender/integrate. But recently I upgraded to androidx as that seemed the way to got. This meant that
<item
android:id="#+id/media_route_menu_item"
android:title="#string/media_route_menu_title"
app:actionProviderClass="android.support.v7.app.MediaRouteActionProvider"
app:showAsAction="always" />
got changed to
<item android:id="#+id/media_route_menu_item"
android:title="#string/media_route_menu_title"
app:actionProviderClass="androidx.mediarouter.app.MediaRouteActionProvider"
app:showAsAction="always"/>
But otherwise, all stays the same for example still CastButtonFactory is used to make the connections. I don't see any button appearing anymore so not sure what is wrong. I still implement AppCompat, have the CastOptions, execute CastContext.getSharedInstance(this). Logging for cast discovery has always been very limited to it is hard to know what is going on.
Related
I applied this notification without knowing what it does. Now UI is missing. It says "Some issues were found while trying to render this preview" while preview and when I run app, It shows a blank surface. How and Where can I configure this?
Finally I find what the notification changes in the project.
when I apllied notificitaion , it adds build.gradle:app to this twice like below.
implementation 'androidx.core:core-ktx:+'
implementation 'androidx.core:core-ktx:+'
Although I have already implemented this
'androidx.core:core-ktx:1.9.0'
This leads rendering problem.
We recently made a number of changes to our CSP and have gotten reports from a very small number of users that the browser is not rendering because of one of these changes. We have 5 reports out of 2mil active users, so this is something very specific.
None of our QA are able to replicate this with their test browsers, so we're unable to determine what about the new CSP is causing the problem.
Is there a way to put a browser into some super strict mode so that it will stop all dynamic content with the slightest issue?
Rundown of my analysis:
I know the latest version also introduced some [tab] unicode, but I want to replicate this issue before I remove it so that I know that we've fixed it.
We do not have any of the deprecated X- headers in there.
Tried loading it into some online CSP validators but those come back with some vulnerabilities, but says the CSP is valid as written.
We're considering the report-to directive but have not implemented yet (Does anyone know if this would even help us in this?)
We were able to screenshare with one of the users with this issue and saw their browser console showing that it was stopping because of the CSP, but it had issues with the CSP that were very old. That user was running a current Chrome install
I'd post the csp but the invalid unicode wouldn't post anyway. It would also identify some of our clients.
I am trying to integrate Glimpse into my existing ASP.NET MVC 5 project. But I cannot see any HUD at bottom right corner as demonstrated in their site. I have all of the assemblies downloaded from NuGet, using Visual Studio 2013 Ultimate and running in localhost.
Can anyone tell me what could be the problem? I am not finding any relevant topic online either.
#Md.lbrahim by looking at the comment replies of you above, it seems that Glimpse is indeed active and rendering its <script> tags.
Can you check with the browser developer tools whether the Glimpse client is actually rendered at the bottom but maybe hidden by another element that has a higher z-index?
If you still can't get the HUD to show up, then maybe create an issue on our issue tracker and try to provide as much details as possible (browser used, versions, other installed packages that might interfere with Glimpse rendering etc...)
When I go on my phone, and type the url to my custom JavaME application, it says "Download". Then I click "Yes". It downloads about 2/3 and then it says Unexpected Error and then quits. How do I fix this?
It could probably be many things, but in the past when I've experienced that particular scenario, it has usually been because of unsupported JAD/MANIFEST attributes.
For example, Nokia has invented a lot of their own attributes you can add for some of their devices. So you'd think that any Nokia-specific JAD/MANIFEST attribute will work on any Nokia phone, or at least be ignored if it's not supported - but that's not the case.
If you try installing a JAR with a MANIFEST that has certain attributes not supported, then it will come up with an install error.
If I were use I'd try removing all special attributes - even if the attribute logically should work - and see if that helps.
Im working on a windows 8 store application so as to send an sms. I have the code running but the i get an error saying "Access Denied" and that my application does not have enough privileges.
Is there any way for me to create my own app (which uses the sms capabilities of the device) and test it out without having to register it with Windows Hardware Dashboard?
This probably means that you need to add the capability to the manifest for your application. If you want to take a look at this, download the sample here (pick any language):
http://code.msdn.microsoft.com/windowsapps/Sms-SendReceive-fa02e55e
What you're looking for is the SMS capability in the manifest. It looks like it doesn't show up in the VS designer, but you can see it in the raw XML. Open the project, and in solution explorer, right click on package.appxmanifest. Then click view source. Near the bottom of the manifest, you'll see this:
<Capabilities>
<DeviceCapability Name="Sms" />
</Capabilities>
Try adding that to your application's manifest. I suspect that's what you're missing.
Thanks,
Ben
This was what I was able to find out :
So by using this process of "Sideloading", you can install apps directly to a device without having to go through the windows store. I will provide the links that got me going in this project,
Sideloading
Discussions
Creating the Metadata
Edit: WDK 8.1 now comes with a new Metadata Authoring tool that is easier/simpler to use. :)