When starting the Xamarin profiler it successfully starts the application on my iPhone device.
However before the profiling begins I get an error at the bottom of the window that states:
Afterwards it states
Sorry something went wrong. An error occurred on client profile while executing a post topic
Any idea how to fix this?
Well something is wrong with the Provision Profile you are creating Either Create it again or Upload a little bit more than this so we can understand what the actual problem is.
Related
Please excuse me for asking a basic question.
I'm using auto translation to ask a question（from Japan）
The app that I had deployed to Heoku suddenly became unusable.
I haven't touched the app at all.
Please refer to the video from the start of the application until the error is displayed, as well as the terminal comments with 'heroku logs --tail' comand.
(the video is edited short. It actually takes about 50 seconds from the start of the application to the display of the error code)
enter link description here
Thank you,
I am currently developing an App for IOS and Android with Xamarin Forms. I am debugging with my Android device.
Starting yesterday, when trying to build and test my solution, it falls into a break state before the App is even loaded.
The exception is:
System.InvalidProgramException: Method wuut.Discover:InitializeComponent () is too complex.
It works when I unplug my Android device and open the App on developer mode. But I really need the Console etc. so right now, I am unable to continue developing my app.
I looked up the exception on Google but couldn't really find anything similar to my problem.
The error occurs inside InitializeComponent on one of my Contentpages containing an AbsoluteLayout.
The AbsoluteLayout is rather big with 5400 Lines of Code. So looking into the error messages, I tried to remove a few chunks of my XAML and it started working again.
So my question is: Does XAML or Xamarin have some limitations on how big an AbsoluteLayout/Contentpage should be? If not, how would I resolve this issue?
Thanks in advance and kind regards
I need to open Xamarin IOS application when clicking on link with my scheme. I have followed this tutorial: https://xamarinhelp.com/uri-scheme/. The solution generally works, but problem occurs when application is already opened. Clicking on link stops application and starts again. Is it expected behavior? How to pass link to application without killing it? I want to use URI scheme solution because it already works across other platforms.
I finally found source of the problem - the base method UIApplicationDelegate.OpenUrl should not be called. It throws exception with message: "Exception of type 'Foundation.You_Should_Not_Call_base_In_This_Method' was thrown."
I have made a Windows Phone app (for WP7.1) that uses BackgroundAudio for streaming, nothing too complicated. It was approved and made available for download in the store. However it no longer works, i.e. the app worked in debug+release when run from VS2012, and I assume the .xap I uploaded worked since microsoft approved it (they rejected it once and I was able to reproduce and fix the bugs they reported).
When downloaded the app simply bails on load on WP8 (lumia 820) i.e. flips back to the tiles immediately.
On WP7 (lumia 800) but the playbutton ignores input, however it downloads and displays the playlist, so some kind of functionality+network connection works.
I have tried the basics: installing using the application-deployment tool (app working), running the "Store Test Kit" which reports some slowdowns in the UI animations, but nothing serious (I hope).
Any ideas how to reproduce ".xap approved and downloaded from store but not working" or getting debug info from the phone without VS? Or any other things i can try out?
Every time your app crashes it will be logged and reported on your Windows Phone Dev Center Account. Just go in there and export the details to excel. Get the stack trace and put it in here. Maybe we can help.
The very first thing i can tell you is the opening page has some exceptions and that too it doesn't go well with some phones. Seriously there are concerns when a wp7 app is ported on wp8 device and vice-verse. To the extent of my knowledge there might be some binding issues. make sure you got the binding class to be public. And just as #AMR mentioned go the dev center and export the stacktrace. Try resolving them. Moreover if an app get certifies, it doesn't mean it is completely error free. The tests are limited to very coomon errors only.
My wp7 app crashes when I come back from a task such as Map, Call or Web Browser. Infact, if i lock my phone and resume it again, still it crashes. Please tell me what could be the problem and how can I remove it?
There is a problem with you code.
Remove the application off the phone by starting a new emulator instance.
Open App.xaml.cs
Put a breakpoint in the method RootFrame_NavigationFailed and Application_UnhandledException
Now use the CallStack to find the root of the issue.
With no code posted (and in your case it could be ANYTHING in the project) you will be the best person to resolve your issue. If you can post a small reproduction on here we can take a look.
In application exit methods you probably should restore the data you dealt with last time before you quited