Common Errors
Because Tinderbox is sort of a "hack" on top of the Tinder API, you may encounter some common errors. Also, some users with older machines or lack of memory can also run into some common errors. These errors are outlined here:
If you're having difficulty starting up Tinderbox and seeing this message, this is an indication that you're using the wrong version of Java. On some machines Java 1.8 works, but occasionally spits out errors. The recommended Java JDK is 1.7.
In later versions of Tinderbox, a commit was merged which checks the version of Java being used to start up the machine and prints an error if there is a version mismatch.
Tinderbox will display this message in the logs when the authentication token with Tinder has expired. To remedy the problem, follow these steps:
- Logout of Tinderbox
- Shut down the app
- Restart the app and log back in
##java.lang.OutOfMemoryError: GC overhead limit exceeded Sometimes the .sbt_config file isn't set when it is installed OR the defaults just aren't enough. Try the following options one-at-a-time in order to resolve the problem:
- Add the following line to the ~/.bash_profile in OSX or Linux:
export _JAVA_OPTIONS="-XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -Xms1024m -Xmx2G -Xss256m -XX:MaxPermSize=4G" - (Mac OSX) Create a file at ~/.sbt_config and paste the contents:
SBT_OPTS="-XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -Xms1024m -Xmx2G -Xss256m -XX:MaxPermSize=4G" - Start up SBT using the command sbt -mem:2048 run (thanks to @damianpoole).
If you continue to have issues, please leave a message here: https://github.com/crockpotveggies/tinderbox/issues/7
##Errors trying to log in
The two images above are very common if there's an issue when you're trying to login. This is almost always caused by a mismatch in the Java version being used to run the app. Tinderbox is built and runs using Java 7, and most often other computers will try to run Java 6 or 8. You can fix this by downloading the appropriate Java JDK version.
##java.util.concurrent.TimeoutException: Futures timed out When using the bot you will see a TimeoutException in Terminal, and some of the functionality such as messages appears to be frozen.
[ERROR] [02/12/2015 19:57:22.802] [application-akka.actor.default-dispatcher-6]
[akka://application/user/UpdatesTask] Futures timed out after [40 seconds]
java.util.concurrent.TimeoutException: Futures timed out after [40 seconds]
at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219)
at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223)
at [LOTS MORE STACK TRACE]
This is actually not a bug with Tinderbox itself, but instead timeouts from the Tinder API. This can be caused either by rate limiting or repeated traffic from Tinder. A quick fix is to logout and log back in by creating a new session. Usually rate limiting is done either by Session Token or IP Address.
If you experience this error, please leave a comment at https://github.com/crockpotveggies/tinderbox/issues/16
##java.io.IOError: java.io.EOFException When using the bot you will get a stack trace that looks like this:
[ERROR] [02/10/2015 10:19:18.195] [application-akka.actor.default-dispatcher-5] [LocalActorRefProvider(akka://application)] guardian failed, shutting down system
java.io.IOError: java.io.EOFException
at org.mapdb.Volume$FileChannelVol.getByte(Volume.java:860)
at org.mapdb.Volume.getUnsignedShort(Volume.java:91)
at org.mapdb.StoreWAL.longStackGetPage(StoreWAL.java:1077)
at [LOTS MORE STACK TRACE]
This is caused by a bug in the internal database known as MapDB. Unfortunately, there is no quick fix for this, and it may be something you'll have to live with until a better DB or updated DB can be placed into the code.
If you experience this error, please leave a comment at https://github.com/crockpotveggies/tinderbox/issues/2