This is primarily used to create small repos that reproduce RubyMotion issues
| Repo | Description | RM Bug |
|---|---|---|
| inheritance_activity | another project that demonstrates a variation of the inheritance problem | RM-773 |
| module_function | module_function can be used as a scope marker, but it won't take a symbol argument |
RM-835 |
| hashbugs | Enumerable is missing many methods |
RMA-755 |
| Repo | Description | RM Bug |
|---|---|---|
| round_rect_crash | Creating an Android RoundRect with Ruby causes an ART crash | RM-871 |
| inheritance | using multiple levels of inheritance breaks if one of the classes is part of module | RM-773 |
| jni_return_type | the compiler does not always assign the correct return type in vendored JAR files | RM-724 |
| support_lib_conflict | Using a PORO with a method named update causes a compile error if you're using the v4 support library |
RMA-724, same as jni_return_type, described above |
| gem_integration | gem specs that expose an Array of file paths are not handled correctly by the Android template code - this pull request resolves this problem but reveals another: module_function and define_method have not been implemented |
RM-805 and RM-806 |
| save_instance | Calling the base class version of Fragment#onSaveInstanceState causes a NoMethodError |
RM-855 |
| inherited_constructors | Constructors that accept parameters are not inherited by subclasses | RM-844 |
| reassign_art_crash | converting a symbol to a string and reassigning to the same variable name causes an ART crash when run in an activity, but works correctly in the REPL | RM-855 |
| gem_dependencies | When using a gem that depends on another gem, the second gem is not correctly pulled into the project | RM-870 |
Older repos: