Remove all UIWebView code? #661

jcesarmobile · 2019-08-29T12:15:49Z

People has started receiving this warning when submitting apps that have references to UIWebView.

ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs.

Doesn't matter if they are using just WKWebView, as long as Apple sees "UIWebView" in the app code, they show the warning, and cordova-ios is full of "UIWebView" references. (Even react native, flutter and Capacitor users have received the warning)

There is currently no solution to this problem for Cordova apps.

So, instead of integrating WKWebView and making it possible to switch from UIWebView to WKWebView on runtime as it was planned, maybe we should just remove all UIWebView code on next major release?

~~There is no deadline, I've contacted an Apple developer that has been tweeting about moving to WKWebView to see if he can provide more information, will update if I get a response.~~

Apple finally announced the deadline:

The App Store will no longer accept new apps using UIWebView as of April 2020 and app updates using UIWebView as of December 2020.

fjaeger · 2019-08-29T13:29:36Z

I am not sure whether it is necessary to remove all the references to UIWebView. There is even some UIWebView code being executed when WKWebView is configured as the main engine. I know at least of CDVUserAgentUtil that is still using UIWebView – independent of the engine configuration.

eun-choi · 2019-08-30T02:29:23Z

It's very important issue in the near future, because UIWebView been deprecated on iOS 13.
That means we would be rejected by App Store Review at some point in the near future.

https://developer.apple.com/documentation/uikit/uiwebview

janpio · 2019-08-30T07:13:49Z

It's very important issue in the near future, because UIWebView been deprecated on iOS 13.
That means we would be rejected by App Store Review at some point in the near future.

That is fortunately not true. Things can be deprecated for a long time before they are removed or their usage affect App Store review.

Which of course does not mean that the previously posted thoughts are wrong in any way - it just doesn't mean this has to lead to problems in the near future. It just definitely could.

nijakobius · 2019-08-30T08:06:12Z

It's very important issue in the near future, because UIWebView been deprecated on iOS 13.
That means we would be rejected by App Store Review at some point in the near future.

That is fortunately not true. Things can be deprecated for a long time before they are removed or their usage affect App Store review.

Which of course does not mean that the previously posted thoughts are wrong in any way - it just doesn't mean this has to lead to problems in the near future. It just definitely could.

UIWebView has been deprecated for well over a year though, so I fear the "long time" is coming to an end very soon. So I'd second that this is a rather urgent issue.

Here's a Twitter thread from one Apple dev on the topic:
https://twitter.com/NiklasMaerz/status/1167031874738434048

dpogue · 2019-08-30T14:19:19Z

Just to set expectations: There's probably about 1 week of full-time work to be done by somebody familiar with the cordova-ios and WKWebView plugin codebases to resolve this issue.

There is currently nobody working full-time on Cordova. We are all volunteers with limited time to contribute.

derman10 · 2019-08-30T14:20:02Z

Same email from Apple to uploading my app to TestFight.

Im building iOS app from ionic 3/cordova and not use UIWebView, just WebView on my config.xml.

<plugin name="cordova-plugin-ionic-webview" spec="^4.0.0" />

Any Solution??

jcesarmobile · 2019-08-30T14:29:17Z

Apple warns because cordova-ios has the UIWebView code, doesn't matter if you use it or not, the code is there.

But it's a warning, we don't know for sure how long will take until Apple starts rejecting apps because of that.

Once they start rejecting apps, the only solution will be to update your cordova-ios version and all plugins that have references to UIWebView to newer versions that don't have those references (they don't exist yet, that's what this issue is for).

fjaeger · 2019-08-30T16:21:17Z

I created a compile-time decision for WKWebView over UIWebView in Pull Request #662

spinninghamster · 2019-08-31T06:38:19Z

iOS 13 will be released around 17 September 2019. Could be that Apple will start rejecting apps after that date.

Starting which version of cordova-ios is WKWevView being used as the default engine? I hear that UIWebView is not being used anymore and WKWebView is the default (but there are still traces of UIWebView), but since which version has this started?

dpogue · 2019-08-31T07:04:00Z

Apple is not going to start rejecting apps that use UIWebView with less than a month of notice. For the moment, it is safe to ignore the warning.

No version of cordova-ios uses WKWebView by default.

spinninghamster · 2019-08-31T07:38:16Z

Apple is not going to start rejecting apps that use UIWebView with less than a month of notice. For the moment, it is safe to ignore the warning.

No version of cordova-ios uses WKWebView by default.

That's somewhat good news.

I was referring to this: https://twitter.com/NiklasMaerz/status/1167031874738434048 where Niklas wrote:

WKWebView is a plugin and UIWebView is part of the core platform. This means we only use WKWebView but there are still unused references of UIWebView in code.

I thought he was speaking about Cordova; but maybe he was speaking about a specific own app.

NiklasMerz · 2019-08-31T07:41:24Z

Just to clarify. I was speaking about our own app with Cordova. We are using the WKwebview plugin and InAppBrowser. I guess many app developers switched to WKwebview by now. Am 31. Aug. 2019, 09:38, um 09:38, Marc <notifications@github.com> schrieb:

…

> Apple is not going to start rejecting apps that use UIWebView with less than a month of notice. For the moment, it is safe to ignore the warning. > > No version of cordova-ios uses WKWebView by default. That's somewhat good news. I was referring to this: https://twitter.com/NiklasMaerz/status/1167031874738434048 where Niklas wrote: > WKWebView is a plugin and UIWebView is part of the core platform. This means we only use WKWebView but there are still unused references of UIWebView in code. I thought he was speaking about Cordova; but maybe he was speaking about a specific own app. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #661 (comment)

fabuhelow · 2019-09-01T13:30:29Z

Same email from Apple to uploading my app to TestFight.

Im building iOS app from ionic 3/cordova and not use UIWebView, just WebView on my config.xml.

<plugin name="cordova-plugin-ionic-webview" spec="^4.0.0" />

Any Solution??

Please follow the following link which will help you to move from UIwebview to WKwebview

https://ionicframework.com/docs/v3/wkwebview/

spinninghamster · 2019-09-01T15:03:06Z

When cordova-ios migrates from UIWebView to WKWebView, how will LocalStorage in apps be handled? Will there be a way to migrate them over?

timbru31 · 2019-09-01T17:22:40Z

That's a good question @spinninghamster! One could argue that a breaking change means no transition of user data, since e.g. plugins for LocalStorage and IndexedDB already exist (e.g., https://github.com/maklesoft/cordova-plugin-migrate-localstorage & https://github.com/pointmanhq/cordova-plugin-ionic-migrate-storage

EdwinRozario · 2019-09-01T21:39:22Z

@fabuhelow Did that solution work for you? My project is running on Ionic 5.1.0. By default its should be using WKWebView. Still receiving the warning. I have tried upgrading to the latest version of cordova-plugin-ionic-webview which is 4.1.1 & updated the config.xml as suggested with no success.

I dont think this issue is due to the app using UIWebview. Any reference of it in any Cordova plugins are causing these warnings. I hope we will be resolved or someone will give us an idea of when it will be resolved.

I have a product release in early October 😞

sts-ryan-holton · 2019-09-03T19:49:28Z

I'd strongly consider prepping some time for this issue, what we don't want is it to suddenly become depreciated upon a later iOS 13 release and then the apps suddenly can't be built, if it's true that it'll take the best part of a week to fix, let's ensure backwards compatibility with older versions of Cordova and ensure that it can truly be fixed promptly when it happens.

I'd further suggest pinning this issue to your repo.

bpresles · 2019-09-03T20:21:22Z

@sts-ryan-holton I've worked already on fixing this potential issue. See PR #663.

EdwinRozario · 2019-09-03T21:18:28Z

Thanks @bpresles . For us working with Ionic, we will to wait for the Ionic team to upgrade cordova-ios in cordova-plugin-ionic-webview before we can start testing this.

janpio · 2019-09-03T21:42:17Z

For us working with Ionic, we will to wait for the Ionic team to upgrade cordova-ios in cordova-plugin-ionic-webview before we can start testing this.

This doesn't make sense. You install cordova-ios into your Cordova app that uses Ionic, but the Cordova iOS version is not set by Ionic and definitely not by cordova-plugin-ionic-webview.

EdwinRozario · 2019-09-03T21:53:20Z

Yes. But cordova-plugin-ionic-webview has a cordova-ios dependency. I thought the plan was to get rid of any reference of UIWebView from project. If simply updating cordova-ios will fix the issue, i will be more than happy.

RichardBoyder · 2019-12-03T11:14:23Z

Hi guys. A Strange Question I know in this forum.. But Are most people moving over to capacitor? Is it Safe to say that the developers who were focusing more on Cordova has taken a slightly different focus? OR Are we Still very serious about Cordova and its future? (Given Apple issues with soon to be deprecated UiWebView.)

This isn't to blame the developers at all , Cordova is brilliant, Its just a simple question Since I now have to make a decision to leave Cordova and go with Capacitor that Ionic has introduced Since Apple Store issue. Business is pushing so its either or ... And I hate to leave Cordova since it has sooooo many awesome plugins and I have built my custom plugin for it which is working wonders.

suraneti · 2019-12-03T11:20:28Z

@RichardBoyder I'm not sure about Capacitor but for Cordova right now is driven by the community.

RichardBoyder · 2019-12-03T12:16:46Z

@RichardBoyder I'm not sure about Capacitor but for Cordova right now is driven by the community.

Understood. Thanks for the reply.

EiyuuZack · 2019-12-09T11:26:59Z

@RichardBoyder I'm not sure about Capacitor but for Cordova right now is driven by the community.

@suraneti what exactly do you mean by this? Does Apache no longer have anything to do with Cordova?

NiklasMerz · 2019-12-09T11:44:56Z

@RichardBoyder I'm not sure about Capacitor but for Cordova right now is driven by the community.

@suraneti what exactly do you mean by this? Does Apache no longer have anything to do with Cordova?

I don't think this is the right place to discuss the Cordova vs Capacitor topic, since this is about an important Cordova issue to be discussed.

I would like to add a short personal note about that nevertheless:

Cordova still an active Apache project worth investing in. It's maintained by volunteers, but probably @suraneti is meaning that nobody is paid to work full-time on Cordova. This means (to me) you may need to be more patient and open to fixing issues and contributing yourself.

RichardBoyder · 2019-12-11T13:27:56Z

All understood. We seriously need a fix for Cordova so we don't have issues when apple decides to cancel our binary uploads. So a very serious matter.

Anyone who can comment and perhaps We can make a path to get it sorted so we don't have to worry about our Cordova apps being rejected in future.. its kind of unnecessary stress on us developers now and I really hope anyone who has Power here to fix this for us will look seriously at this issue. Please need a answer. Will we be able to rest in the knowledge that this will be sorted within next 2 months or so... ? I'm asking the Cordova Devs here who can do it and who can push a new major version of Cordova so we can all implement this?

RichardBoyder · 2019-12-11T13:29:25Z

@RichardBoyder I'm not sure about Capacitor but for Cordova right now is driven by the community.

@suraneti what exactly do you mean by this? Does Apache no longer have anything to do with Cordova?

I don't think this is the right place to discuss the Cordova vs Capacitor topic, since this is about an important Cordova issue to be discussed.

I would like to add a short personal note about that nevertheless:

Cordova still an active Apache project worth investing in. It's maintained by volunteers, but probably @suraneti is meaning that nobody is paid to work full-time on Cordova. This means (to me) you may need to be more patient and open to fixing issues and contributing yourself.

I wish I had the skills to fix this haha (I don't) ... otherwise I would be doing it right now... So many hundreds of people are relying on Cordova for their apps on store and I'm sure everyone is worried.

spinninghamster · 2019-12-11T13:29:51Z

All understood. We seriously need a fix for Cordova so we don't have issues when apple decides to cancel our binary uploads. So a very serious matter.

Anyone who can comment and perhaps We can make a path to get it sorted so we don't have to worry about our Cordova apps being rejected in future.. its kind of unnecessary stress on us developers now and I really hope anyone who has Power here to fix this for us will look seriously at this issue. Please need a answer. Will we be able to rest in the knowledge that this will be sorted within next 2 months or so... ? I'm asking the Cordova Devs here who can do it and who can push a new major version of Cordova so we can all implement this?

It has already been fixed. Read:
https://cordova.apache.org/announcements/2019/11/25/cordova-ios-release-5.1.0.html

RichardBoyder · 2019-12-11T13:33:05Z

Unfortunately not (well it didn't work for me at least ). Moved to 5.1.0 ages ago when it came out and still get the apple warning. did everything recommended there and its still happening when push to store.

breautek · 2019-12-11T13:35:38Z

Unfortunately not. Moved to 5.1.0 ages ago when it came out and still get the apple warning. did everything recommended there and its still happening when push to store.

Then you likely have a plugin that still references UIWebview api. A common one that I can think of is the inappbrowser plugin. So I would inspect your plugins.

RichardBoyder · 2019-12-11T13:37:19Z

Unfortunately not. Moved to 5.1.0 ages ago when it came out and still get the apple warning. did everything recommended there and its still happening when push to store.

Then you likely have a plugin that still references UIWebview api. A common one that I can think of is the inappbrowser plugin. So I would inspect your plugins.

That is very true. Could be the case. I guess the plugin authors haven't updated their plugins yet to sort this out. But could certainly find and comment out I guess in the interim ... if it doesn't break the app.

jacobweber · 2019-12-23T17:20:06Z

OK, the deadline is upon us:

The App Store will no longer accept new apps using UIWebView as of April 2020 and app updates using UIWebView as of December 2020.

spinninghamster · 2019-12-24T05:59:46Z

OK, the deadline is upon us:

The App Store will no longer accept new apps using UIWebView as of April 2020 and app updates using UIWebView as of December 2020.

Now: "Oh, a year of time ..all good"

In November 2020: "Oh my god, we're running out of time! The 10 most popular Cordova plugins are all not updated yet!"

desmeit · 2019-12-27T10:56:37Z

@breautek Is there a way to search the plugins to find UIWebview api? What is the exact keyword? Just "UIWebview"? I think it is just a problem with the 3.1.0 version of inappbrowser plugin.

desmeit · 2020-02-28T13:24:38Z

In my case the following plugins caused the issue:

facebook4 3.1.0
Googleplus 7.0.1
cordova-plugin-decimal-keyboard

i tested it step by step. delete plugin by plugin one after the other until the message disappears. not nice, but I couldn't find out otherwise.

JamesCoyle · 2020-03-03T17:25:28Z

I've recently created a new Cordova project specifically for iOS and I'm getting this issue. I'm using cordova-ios v5.1.1 and the only plugin I'm using is cordova-plugin-whitelist v1.3.4. What can I do about this?

breautek · 2020-03-03T17:47:49Z

I've recently created a new Cordova project specifically for iOS and I'm getting this issue. I'm using cordova-ios v5.1.1 and the only plugin I'm using is cordova-plugin-whitelist v1.3.4. What can I do about this?

Add a wkwebview plugin such as this one.

Do pay attention to the required config.xml settings.

Do note that plugin is a stopgap, it won't be needed in the next major release of cordova-ios, which will only support wkwebview, and it will be built-in.

If you have any further questions, don't be afraid to drop by our slack

KevinKelchen · 2020-03-03T18:16:34Z

I want to give a big THANK YOU to ALL of the contributors (@erisu, @jcesarmobile, etc.) who have helped in any way to add the feature that removes UIWebView references at compile-time.

Just this past week we began receiving emails from Apple about our existing app having UIWebView references even though we were using WKWebView to host our app. We were able to make a small version bump to cordova-ios and opt-in with the new flag and it worked beautifully! No more emails from Apple!

FWIW, these are the plugins we have in our project:

"plugins": {
  "cordova-plugin-cartegraph-datepicker": {},
  "cordova-plugin-device": {},
  "cordova-plugin-safariviewcontroller": {},
  "cordova-plugin-whitelist": {},
  "cordova-plugin-screen-orientation": {},
  "cordova-plugin-splashscreen": {},
  "cordova-plugin-statusbar": {},
  "cordova-sqlite-ext": {},
  "cordova-plugin-network-information": {},
  "cordova-plugin-geolocation": {},
  "cordova.plugins.diagnostic": {
    "ANDROID_SUPPORT_VERSION": "26.+"
  },
  "cordova-plugin-camera": {},
  "com-sarriaroman-photoviewer": {},
  "cordova-plugin-image-resizer": {},
  "cordova-plugin-customurlscheme": {
    "URL_SCHEME": "cgone",
    "ANDROID_SCHEME": " ",
    "ANDROID_HOST": " ",
    "ANDROID_PATHPREFIX": "/"
  },
  "cordova-plugin-ionic-keyboard": {},
  "cordova-ios-plugin-no-export-compliance": {},
  "cordova-plugin-ionic-webview": {
    "ANDROID_SUPPORT_ANNOTATIONS_VERSION": "27.+"
  },
  "cordova-plugin-wkwebview-inject-cookie": {},
  "cordova-plugin-cartegraph-cookie-master": {}
}

I appreciate the volunteer work of Cordova maintainers and contributors who spend personal time outside of their day jobs to help keep things running smoothly for us! ❤️

khayargoli · 2020-03-10T10:08:51Z

@KevinKelchen Does this mean that anyone using cordova-ios: 5.1.1 and usage of latest plugins will be able to pass app submission sucessfully? Don't we have to remove UIWebView instances manually?

KevinKelchen · 2020-03-10T15:17:36Z

@Biswas123, using cordova-ios 5.1.1 and the new flag will remove UIWebView references automatically for you at compile-time, but it's just those UIWebView references that are part of cordova-ios.

If you use other plugins that themselves reference UIWebView, removing those UIWebView references has to be addressed separately by those plugins; updating cordova-ios and using the new flag will not inherently remove those references.

We did not have any plugins that referenced UIWebView so updating cordova-ios was all that was necessary for us to pass app validation successfully.

mcastets · 2020-03-11T16:57:31Z

Does anyone know how to check if a build still reference UIWebView like Apple do?

I have tried to unzip my Appname.ipa file then run grep -lr "UIWebView" *.
It returns a line like Payload/MyApp.app/MyApp. Does it mean my build won't pass Apple check?

Even better, how to know which plugins still reference UIWebView?

KevinKelchen · 2020-03-11T17:16:16Z

I don't know enough to comment on analyzing the app binary to know whether it will contain UIWebView usages that Apple won't like.

As far as plugins go, you could search the plugins directory of your repo after a cordova prepare to see if any plugins use UIWebView.

Otherwise you could try uploading your build to Apple TestFlight.

At least for us, we started receiving an email from Apple with every single upload to TestFlight. After we updated cordova-ios and used the new flag those emails completely went away. That was good enough evidence for us.

If you're not using TestFlight or you're not already getting emails from Apple about UIWebView from your uploads to TestFlight, this technique may not work well. But the "proof in the pudding" of whether your app contains any UIWebView-related stuff Apple wouldn't like is to actually run it through Apple's validation and see if it gets flagged (upload to TestFlight or submit the app to the App Store).

nulele · 2020-03-16T10:50:55Z

I don't know enough to comment on analyzing the app binary to know whether it will contain UIWebView usages that Apple won't like.

As far as plugins go, you could search the plugins directory of your repo after a cordova prepare to see if any plugins use UIWebView.

Otherwise you could try uploading your build to Apple TestFlight.

At least for us, we started receiving an email from Apple with every single upload to TestFlight. After we updated cordova-ios and used the new flag those emails completely went away. That was good enough evidence for us.

If you're not using TestFlight or you're not already getting emails from Apple about UIWebView from your uploads to TestFlight, this technique may not work well. But the "proof in the pudding" of whether your app contains any UIWebView-related stuff Apple wouldn't like is to actually run it through Apple's validation and see if it gets flagged (upload to TestFlight or submit the app to the App Store).

Same problem.
Sorry @KevinKelchen but I don't understand what "flag" are you talking about... where do I have to opt-in that flag?

And this solution works for "cordova-plugin-ionic-webview" too or only "for cordova-plugin-wkwebview-engine"? I have installed the first.

Thanks

erisu · 2020-03-16T12:08:49Z

Use cordova-ios@5.1.1
Add preference flag WKWebViewOnly to the config.xml.

Must use a WKWebView plugin.
The following example uses the cordova-plugin-wkwebview-engine plugin:

Add plugin cordova-plugin-wkwebview-engine, preferably the latest version 1.2.1
Add preference attribute CordovaWebViewEngine to the config.xml.
Add feature attribute CDVWKWebViewEngine to the config.xml.

Example config.xml with cordova-plugin-wkwebview-engine plugin

<platform name="ios">
    <preference name="WKWebViewOnly" value="true" />

    <feature name="CDVWKWebViewEngine">
        <param name="ios-package" value="CDVWKWebViewEngine" />
    </feature>

    <preference name="CordovaWebViewEngine" value="CDVWKWebViewEngine" />
</platform>

Still getting the warning?
If you are still getting the warning, most likely a plugin that you are using still references UIWebView. You will need to identify which plugin and contact the plugin developers on their support channel (plugin's repo) and request them to fix it. They can either remove the references or make use of this flag to wrap the references.

All official Cordova plugins were updated to use the flag.

Using Ionic WKWebView plugin?
If you are using Ionic's plugin, I believe the UIWebView references have already been removed from their latest version.

Make sure you are using the latest version.
Make sure the WKWebViewOnly flag is set still for cordova-ios platform.

The other preference and feature arguments seen in the example above are from cordova-plugin-wkwebview-engine and may not be needed for Ionic.

If you have any issue or usage questions with the Ionic plugin. Read their docs and request help from their support channels.

jcesarmobile changed the title ~~Remove al UIWebView code?~~ Remove all UIWebView code? Aug 29, 2019

jcesarmobile mentioned this issue Aug 29, 2019

iOS Deprecated API Usage Warning ionic-team/cordova-plugin-ionic-webview#428

Closed

fjaeger mentioned this issue Aug 30, 2019

Optional compile-time decision for WKWebView over UIWebView #662

Closed

flean mentioned this issue Aug 30, 2019

Cordova-iOS UIWebView meteor/meteor#10683

Closed

bpresles mentioned this issue Sep 2, 2019

Fix #661: Removed all UIWebView code. #663

Closed

5 tasks

janpio mentioned this issue Sep 2, 2019

WKWebView built-in support status #534

Closed

This was referenced Sep 3, 2019

Cordova "Apple will stop accepting submissions of apps that use UIWebView" warning when submitting to app store apache/cordova#148

Closed

Depreciated API error from Apple apache/cordova-plugin-inappbrowser#532

Closed

claustres mentioned this issue Sep 3, 2019

UIWebView API deprecation notice kalisio/kdk#47

Closed

dpa99c mentioned this issue Jan 7, 2020

ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs dpa99c/cordova-plugin-firebasex#266

Closed

line72 mentioned this issue Jan 7, 2020

Fix Touch Issues on iOS 13 line72/montclair-pwa-ios#4

Closed

dertieran mentioned this issue Jan 28, 2020

Support WKWebViewOnly build settings EddyVerbruggen/cordova-plugin-3dtouch#45

Merged

erisu mentioned this issue Jan 29, 2020

refactor: drop uiwebview & add wkwebview #773

Merged

1 task

erisu closed this as completed in #773 Feb 10, 2020

apache locked as resolved and limited conversation to collaborators Mar 16, 2020

Remove all UIWebView code? #661

Remove all UIWebView code? #661

Comments

jcesarmobile commented Aug 29, 2019 • edited Loading

fjaeger commented Aug 29, 2019

eun-choi commented Aug 30, 2019 • edited Loading

janpio commented Aug 30, 2019

nijakobius commented Aug 30, 2019

dpogue commented Aug 30, 2019

derman10 commented Aug 30, 2019

jcesarmobile commented Aug 30, 2019

fjaeger commented Aug 30, 2019

spinninghamster commented Aug 31, 2019 • edited Loading

dpogue commented Aug 31, 2019

spinninghamster commented Aug 31, 2019

NiklasMerz commented Aug 31, 2019 via email

fabuhelow commented Sep 1, 2019

spinninghamster commented Sep 1, 2019

timbru31 commented Sep 1, 2019

EdwinRozario commented Sep 1, 2019 • edited Loading

sts-ryan-holton commented Sep 3, 2019 • edited Loading

bpresles commented Sep 3, 2019

EdwinRozario commented Sep 3, 2019

janpio commented Sep 3, 2019

EdwinRozario commented Sep 3, 2019

RichardBoyder commented Dec 3, 2019

suraneti commented Dec 3, 2019 • edited Loading

RichardBoyder commented Dec 3, 2019

EiyuuZack commented Dec 9, 2019

NiklasMerz commented Dec 9, 2019

RichardBoyder commented Dec 11, 2019

RichardBoyder commented Dec 11, 2019

spinninghamster commented Dec 11, 2019

RichardBoyder commented Dec 11, 2019 • edited Loading

breautek commented Dec 11, 2019

RichardBoyder commented Dec 11, 2019

jacobweber commented Dec 23, 2019

spinninghamster commented Dec 24, 2019

desmeit commented Dec 27, 2019 • edited Loading

desmeit commented Feb 28, 2020

JamesCoyle commented Mar 3, 2020

breautek commented Mar 3, 2020 • edited Loading

KevinKelchen commented Mar 3, 2020

khayargoli commented Mar 10, 2020 • edited Loading

KevinKelchen commented Mar 10, 2020

mcastets commented Mar 11, 2020 • edited Loading

KevinKelchen commented Mar 11, 2020

nulele commented Mar 16, 2020 • edited Loading

erisu commented Mar 16, 2020 • edited Loading

jcesarmobile commented Aug 29, 2019 •

edited

Loading

eun-choi commented Aug 30, 2019 •

edited

Loading

spinninghamster commented Aug 31, 2019 •

edited

Loading

EdwinRozario commented Sep 1, 2019 •

edited

Loading

sts-ryan-holton commented Sep 3, 2019 •

edited

Loading

suraneti commented Dec 3, 2019 •

edited

Loading

RichardBoyder commented Dec 11, 2019 •

edited

Loading

desmeit commented Dec 27, 2019 •

edited

Loading

breautek commented Mar 3, 2020 •

edited

Loading

khayargoli commented Mar 10, 2020 •

edited

Loading

mcastets commented Mar 11, 2020 •

edited

Loading

nulele commented Mar 16, 2020 •

edited

Loading

erisu commented Mar 16, 2020 •

edited

Loading