-
The puck is a tricky fellow.
We've had (and continue to have) issues with the user location puck, the map camera, and the user location not always being in sync.
### Background info
I think t…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
Hello, thanks for putting this package together. I have a basic example here which attempts to open a route with series of waypoints in Google and Apple Maps. This works fine in Google, but not in App…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…
-
```
PowerMock may consume a lot of memory due to the Javassist classpool. We do
detach on the CtClass after it's use but perhaps we need to re-instantiate
the ClassPool after each test case to free up…