I have tried different samples apps and I am getting the same error. If I create a new team app it works fine but if I remove the app from AppStudio or teams, then I cannot install/execute the app again.
I am using visual studio code with a simple Teams Tab Application code.
This is the error in teams (web with Chrome or Edge)
"App not found, Please verify the app and it's access permissions".
This is the main log error:
TypeError: Cannot read property 'customBots' of undefined
at Function.t.getAppAnalyticsData (https://statics.teams.cdn.office.net/hashed/3.1-app.min-46191d5.js:1:3875125)
at e.getAppInformationForTelemetry (https://statics.teams.cdn.office.net/hashed/lazy-ng1-mod-extensibility-dialogs.min-4642d77.js:1:202134)
at e.logViewAppActionForTelemetry (https://statics.teams.cdn.office.net/hashed/lazy-ng1-mod-extensibility-dialogs.min-4642d77.js:1:200224)
at https://statics.teams.cdn.office.net/hashed/lazy-ng1-mod-lpc-services.min-72bf322.js:1:134587 undefined
Presumably you are using Teams Toolkit? If so, when you create the app in Visual Studio/ Visual Studio Code it is ALSO creating an app in App Studio in your personal account behind the scenes. If you choose to DELETE that app in App Studio, then Teams Toolkit has nothing behind the scenes to hook in to to redeploy. I think (can't check right now) that the app source code will have a manifest file somewhere - you can add this manually back to App Studio using the "import" function.
Related
I have written a Flutter app which implements several deep links with package uni_links. The deep links work correctly with adb commands. Then I created actions.xml in this path:
D:\Android\AndroidStudioProjects\FlutterProjects\garage_controller\android\app\src\main\res\xml\actions.xml
I also added the following lines in AndroidManifest.xml:
<meta-data
android:name="com.google.android.actions"
android:resource="#xml/actions" />
Android Studio highlighted "#xml/actions" in red and complains that it cannot resolve the symbol. I have other parts of AndroidManifest highlighted red. I guess these errors are because of Flutter.
I uploaded the app to Google Play and started internal testing. When I ran App Action Test Tool (AATT), I got the following error:
No Android Module with actions file reference found. You need one Android Module with an actions file reference.
My questions are:
Does App Actions work in a Flutter App?
Does AATT work on a Flutter App?
Why do I get the "cannot resolve symbol" error for "#xml/actions"? I think I put everything in the right place. Thanks for your help.
I got it fixed. Basically everything was done correctly in my Flutter app. The path of actions.xml was also correct. The issue is with AATT which does not know where to find actions.xml in a Flutter app. I just had to open the Android portion of the app in Android Studio. Then AATT knew where to find the file. Google did not put a lot of AI in its tool. More details in here: https://issuetracker.google.com/issues/204233238
I have Visual Studio Enterprise license issued by my Employer. I am using the MacBook Pro provided by them which is already enrolled for mobile device management with my email id by my employer with Microsoft Intunes Company Portal.
But every time I try to login to my account in VS, I get an error saying Your login was successful but your admin requires your device to be managed by MyEmployer to access this resource.
My device is already enrolled with MDM profile. I reported this issue as a service request in our IT support. But they have no idea of the actual error.
Please let me know if I am doing anything wrong or need additional steps.
Sounds like your IT has configured Conditional Access incorrectly for Visual Studio. They should check the Conditional Access controls in Azure AD, and could also try unenrolling/reenrolling your device.
If IT can't resolve the issue, they should contact Microsoft Support who would be more helpful than StackOverflow.
Updating to Visual Studio for Mac 8.6 released on May 19, 2020 (today) fixed my issue. Their release notes state the following for Shell. Learn more at this link
Shell
Visual Studio for Mac now has new identity libraries that should
ease many of the issues that users have faced signing in. In addition,
Visual Studio for Mac now supports device code authentication and
system browser. You can enable these two options in Preferences should
you need them. As a result of the new authentication flow, users who
have been signed in previously will need to re-authenticate.
i integrated crashlytics into my unity game, everything worked fine, but then i had to change my package name and my working mail, since then whenever i open the dashboard it gives me an alert "Sorry the app could not be located".
I reinstalled the crashlytics sdk in unity, used new login in prepare fabric tab, but the issue is still there, although the crashlytics seems to be working.
Thanks. Usually this means we aren't detecting the build and run event. Please make sure you are building and running in the relevant IDE. Also, clean your app and dependencies in the native IDE to make sure the bundle ID is updated in all locartions. If you still run into issues, you will need to contact support as your app may be in a weird state in our system.
I'm trying to play with a Simple ARCWelder example using Google Maps but I keep getting Unrecognized manifest key 'arc_metadata'.
I've done the following:
Created a sample Android app via Android Studio that uses Google Maps API 2. The Android app is a barebones basic app with a single MainActivity with uses SupportMapFragment. I'm very familiar with this process, and everything runs up fine on an actual device (N6), with Google Maps working correctly
I've taken the debug apk from point 1, and am trying to use ARC Welder to run it within Chrome.
As I'm using Google Play Services, I've generated an OAuth Client ID within console.developers.google.com for my project and have copied and pasted this into ARC Welder
I've created a package on ChromeWebStore, and have published it as private available to internal testers, and later to public but it made no difference
I'm running Chrome v46 and have enabled Developer Mode
I've taken the public key from my chrome WebStore entry, stripped out line breaks etc, and my Additional Metadata in ARCWelder looks like this:
{"crx_key":"XXXXXXX","usePlayServices":["location","maps"]}
The result under chrome://extensions:
There were warnings when trying to install this extension:
Unrecognized manifest key 'arc_metadata'.
Also, TESTing my app under ARC Welder does not run up my app.
Would appreciate if anyone can offer any other suggestions?
Announcement
Google will no longer support Chrome App.Maybe you should try to run it on a lower version of chrome.
I have installed the Titanium Developer 1.2.2 form my login account (on Mac system) and have done one demo project. I was able to see that working in the iPhone simulator. Now if I switch user and login to another account to run Titanium Developer there, it downloads and runs there but I am unable to launch any project there. The SDK Version simply shows as 'loading...'.
As a work around I opened a terminal window and typed sudo abhilash (assuming my login name is 'abhilash') and entered password and launched the Titanium from command line. It opened my instance of titanium and detected the SDK version properly as 4.2 and when I click launch in simulator, it throws the following error
Now how do I make it working for the second user account? I have triend re-installing the xcode and titanium from the second user's account but no success :(
Kindly help!!
It doesn't answer your question specifically but this post was helpful for me in enabling Titanium to be used across different user accounts. I suspect you may have already tried this since I couldn't even get Titanium to open in another user account
http://developer.appcelerator.com/question/21121/titanium-crashing-on-startup-on-mac
the other thing to try is to create a new project in the new users account and then copy the contents of the "Resources" directory into the newly created project. I found this also fixed an issue of opening an old project.