Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Martz
    @Martz2804_twitter
    Ok, I'll revert then. Thanks
    Gekidoku
    @Gekidoku

    @jonathanpeppers Thought you would want an update, In the end it was a combination of the conditions my users were in, and me apparently scuffing up.
    Part 1. Apparently my users were often times in an area where they only barely had a 3G connection, Thus the default timeout time of the http client was too short for requests to complete, Solution, make the timeout a bit longer.

    Part 2, Me scuffing up,
    Apparently i had some debug code in the server on certain requets, IE the ones that are called in onresume and onstart, that in certain edge cases, (No/wrong permissions on database/tables,) it would return an empty string, Now i allowed the Json parsing to go through if the result was not null and it was not "offline", So the deserializer got passed an empty string, the model it had to deserialize to had only nullable values so it passed, but then if i tried to get an element of the model it would nullref. Fixed by not being dumb and returning null instead. This was also the case in my async GET manager. that would return an empty string instead of null.

    Lessons learned,
    Use the custom error tracing that appcenter provides,
    Call the clients that its crashing for.

    IoTFier
    @IoTFier
    Hi @jonpryor , @Redth , @dalexsoto and @jonathanpeppers - any guidance on detecting the issue behind an error - android.util.AndroidRuntimeException: Animators may only be run on Looper threads
    at android.animation.AnimatorSet.start(AnimatorSet.java:705)
    at android.animation.AnimatorSet.start(AnimatorSet.java:684) ? I don't know which of my new nuget package updates may have caused this. The same XF App on iOS works just fine. Your thoughts will be appreciated.
    Shane Neuville
    @PureWeen

    That exception is basically saying that piece of code needs to run on the ui thread. That's what the looper thread is.

    So something in your code is triggering off the ui thread that needs to be marshaled to the ui thread

    IoTFier
    @IoTFier
    Hi @PureWeen - thank you. There was no change on my code. I located the issue. It is due to the latest update of the Syncfusion SfTabView control to the latest version 17.4.0.40 , and as a result it is throwing that error randomly on selecting SfTabItems (tab item 3 onward). Downgrading that version to 17.4.0.39 removed that error. An incident report on Syncfusion support is created. Anyone here from syncfusion or @syncsiva to look into this ?
    Tomasz Cielecki
    @Cheesebaron
    Uhm. Would be really nice if xamarin/xamarin-android#4062 got fixed. It is only 1 out of maybe 10 builds that succeed because R.java in some lib is used by some other process, for MvvmCross. It is a waste of time and resources triggering build after build to get something through...
    Jonathan Peppers
    @jonathanpeppers
    @Cheesebaron
    We have a PR for this if you think it is the same: xamarin/xamarin-android#4043
    a workaround is to downgrade to Xamarin.Build.Download 0.4.11
    the latest XBD is someone getting duplicate AndroidResource folders and causes this
    but we are fixing both sides
    Tomasz Cielecki
    @Cheesebaron
    Yeah I just searched a bit and found your issue
    Seems similar
    Will try your workaround
    Thanks!
    Tomasz Cielecki
    @Cheesebaron
    I've triggered a new build with the downgrade, hopefully this works 🤞
    Tomasz Cielecki
    @Cheesebaron
    @jonathanpeppers thank you so much. It worked!
    Jonathan Peppers
    @jonathanpeppers
    :thumbsup: we should hopefully have a fix soon as everyone gets back from the holidays
    Jonathan Dick
    @Redth
    yeah we have a PR for XBD already, just needs to be reviewed/merged/published xamarin/XamarinComponents#774
    IoTFier
    @IoTFier
    Hi @Redth - is the Xamarin component - https://github.com/xamarin/XamarinComponents/tree/master/Util/Xamarin.Build.Download - designed only for native or can it be also used in the Xamarin Forms solution a/c all platform projects including UWP ?
    Jonathan Dick
    @Redth
    i'm not entirely sure what you mean? what's the use case?
    IoTFier
    @IoTFier
    I meant can this component be referred in android, ios and UWP projects withing XF solution ? I'm trying to get familiar with the capability provided by this component.
    Daniel Cazzulino
    @kzu
    seems like our templates should do that by default so things "just work" when developing locally (maybe inside an #if DEBUG?)
    Jon Douglas
    @JonDouglas
    we can definitely add the cleartext addition in our templates. Let me add an issue there.
    Daniel Cazzulino
    @kzu
    there is already one
    Jon Douglas
    @JonDouglas
    i added a github issue and will refer these items over
    Jonathan Peppers
    @jonathanpeppers
    @kzu make sure you just enable SSL - don't do anything to turn if off in the app
    we shouldn't be pushing anyone to use http
    Daniel Cazzulino
    @kzu
    nono, the problem isn't that. It's that the dev cert from asp.net isn't trusted
    it is SSL
    Jonathan Peppers
    @jonathanpeppers
    there still might need to be a clear comment that says "don't do this in production"
    it depends on what the change is though, if it somehow only allows the service running on localhost
    the emulator won't know it's localhost, though
    Brendan Zagaeski
    @brendanzagaeski
    Huh. Maybe there are desktop .NET client templates for ASP.NET that show the preferred approach to solve that?
    Jonathan Pobst
    @jpobst
    traditionally they have made it super hard to run asp.net for !localhost
    maybe they have finally had to relent for Docker
    Alexander Köplinger
    @akoeplinger
    afaik the dotnet sdk generates a localhost certificate and registers that in the system cert store
    I guess you need to somehow propagate that to android
    Jonathan Pobst
    @jpobst
    so there's 2 issues: only allowing traffic to localhost, and only allowing SSL traffic
    Brendan Zagaeski
    @brendanzagaeski
    Oh, that makes sense. Interesting.
    IoTFier
    @IoTFier
    while deploying XF app to a 32 bit pixel3a emulator, I am getting an error System.ArgumentException: Illegal characters in path. Any thoughts to resolve this ?
    Severity Code Description Project File Line Suppression State
    Error XARDF7004: System.ArgumentException: Illegal characters in path.
    at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)
    at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, String fullPath, Boolean checkForDuplicates, Boolean needFullPath)
    at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
    at Xamarin.Android.Tasks.RemoveDirFixed.RunTask()
    at Xamarin.Android.Tasks.AndroidTask.Execute() 0
    IoTFier
    @IoTFier
    Hi @JonDouglas , @jonpryor , @Redth - any thoughts on my request above ? I am using VS 16.4.2 ; not having any issue with deployment of the app on iOS simulator.
    Jonathan Peppers
    @jonathanpeppers
    @IoTFier the error message you're getting there will be improved by: xamarin/xamarin-android@c0c3cb1
    But it seems like the build can't delete a directory
    Can you delete that file manually in File Explorer?
    Frank Szendzielarz
    @FrankSzendzielarz

    Hi folks. We're looking to move a discussion from StackOverflow somewhere where we might get help. Basically for Android since upgrading Xamarin.Forms components we're no longer getting push notifications handled when the app is stopped (not force stopped, not in Doze mode). Worked for earlier 3.? versions, not anymore. The SO conversation is in the comments section here https://stackoverflow.com/questions/59582314/how-can-i-receive-a-push-notification-when-my-xamarin-android-app-is-stopped

    Have folks here in the last 3 or 4 months run into any known Firebase/Xamarin issues that might help? Is this a forms thing or OK to discuss here?

    Jonathan Peppers
    @jonathanpeppers
    @FrankSzendzielarz when you updated Xamarin.Forms did other NuGet packages update?
    Like the support libraries, google play services, etc.
    Looking at the code on the stack overflow post, I would add logging throughout
    You need to know exactly which point things fail, by looking at adb logcat output
    Matthew
    @MattVon
    Hey @jonathanpeppers , I can't speak for Frank for his project but the source code shown in the StackOverflow posts is part of 2 projects. In my case, my work project and my sample project. Source code, NuGet packages (relevant to push) and any dependencies match across both the work project and the sample project, yet only the sample project works. That said, as in Franks experience my work project also had an update of XF from 3.6 to 4.x - that's the only thing that has sprung to my mind at the moment. I've used AppCenter logging but nothing happens, for my end I'll check adb logcat - I don't quite know how it works yet but hopefully Frank can add more input from his experience.
    Jonathan Peppers
    @jonathanpeppers
    The logging is so you can know how far it gets before it fails
    Since you are testing a notification when the app is closed you can't just use the IDE's debugger, adb logcat is a good option there
    When I implemented push in apps in the past, I had logging all over it, even in the production App Store build