puelo

Results 28 comments of puelo

The suggestion @blaskovicz is mentioning is indeed working. I was also able to locate the "source" of the problem inside the directive itself, but was unable to solve it (mostly...

I have a somewhat desireable solution to the scrolling problem on mobile devices: I am using a seperate movement listener for touch movements like this: ``` javascript angular.element($document).bind('touchmove', touchMoveListen); ```...

Can second this. Happened on Samsung Galaxy S9 (Android 8.0): ``` java.lang.RuntimeException: at android.app.ActivityThread.deliverResults (ActivityThread.java:4489) at android.app.ActivityThread.handleSendResult (ActivityThread.java:4532) at android.app.ActivityThread.-wrap20 (Unknown Source) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1752) at android.os.Handler.dispatchMessage (Handler.java:105) at android.os.Looper.loop...

I believe that this problem is realted to some changes made on the Twitter side and is not caused by this library. Read: https://twittercommunity.com/t/callback-url-not-approved-but-worked-for-months/107261 And: https://developer.twitter.com/en/docs/basics/developer-portal/guides/callback-urls.html in short (for Android):...

I initially closed the issue, because i thought that it wasn't possible to proxy a private repo through to the application to update, but now i read that it should...

I tried to debug `now` with a **public** repository and this is what it says: > [debug] Retrying: Error: An unexpected internal error occurred Error: An unexpected internal error occurred...

@onekiloparsec Yeah i think my problem is not related to the private repository since i also cannot deploy when using a public repository.

I am not saying that this is not a bug (or maybe should work), but i think you can work around that by doing this: ``` abstract class BaseResolver {...

> since in some cases you don't exactly know what the subclasses are at compile time How so? Regarding the issue: I guess it make make sense to check for...

> In situations with dynamic linking or as part of a library. I see. Although those could probably still just write their own resolvers (extending your base resolver) when extending...