JRebel for Android doesn't install app

ZeroTurnaround Homepage Forums JRebel Support JRebel for Android doesn't install app

This topic contains 4 replies, has 2 voices, and was last updated by  Mateus M. 6 months, 1 week ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #62654

    Mateus M.
    Member

    Hi, everyone. Always when I try to install app using my device on Android Studio, I get this error:

    12:39:40 Preparing application… This may take a minute.
    12:39:50 JRebel for Android terminated: Cannot Run with JRebel for Android: Starting: Intent { cmp=jra.com.example.mateus.testeappkt/com.zeroturnaround.jrebel.android.agent.companion.CompanionStatusActivity }
    usage: am [subcommand] [options]
    usage: am start [-D] [-N] [-W] [-P <FILE>] [–start-profiler <FILE>]
    [–sampling INTERVAL] [-R COUNT] [-S]
    [–track-allocation] [–user <USER_ID> | current] <INTENT>
    am startservice [–user <USER_ID> | current] <INTENT>
    am stopservice [–user <USER_ID> | current] <INTENT>
    am force-stop [–user <USER_ID> | all | current] <PACKAGE>
    am kill [–user <USER_ID> | all | current] <PACKAGE>
    am kill-all
    am broadcast [–user <USER_ID> | all | current] <INTENT>
    am instrument [-r] [-e <NAME> <VALUE>] [-p <FILE>] [-w]
    [–user <USER_ID> | current]
    [–no-window-animation] [–abi <ABI>] <COMPONENT>
    am profile start [–user <USER_ID> current] [–sampling INTERVAL] <PROCESS> <FILE>
    am profile stop [–user <USER_ID> current] [<PROCESS>]
    am dumpheap [–user <USER_ID> current] [-n] <PROCESS> <FILE>
    am set-debug-app [-w] [–persistent] <PACKAGE>
    am clear-debug-app
    am set-watch-heap <PROCESS> <MEM-LIMIT>
    am clear-watch-heap
    am bug-report [–progress]
    am monitor [–gdb <port>]
    am hang [–allow-restart]
    am restart
    am idle-maintenance
    am screen-compat [on|off] <PACKAGE>
    am package-importance <PACKAGE>
    am to-uri [INTENT]
    am to-intent-uri [INTENT]
    am to-app-uri [INTENT]
    am switch-user <USER_ID>
    am start-user <USER_ID>
    am unlock-user <USER_ID> [TOKEN_HEX]
    am stop-user [-w] [-f] <USER_ID>
    am stack start <DISPLAY_ID> <INTENT>
    am stack movetask <TASK_ID> <STACK_ID> [true|false]
    am stack resize <STACK_ID> <LEFT,TOP,RIGHT,BOTTOM>
    am stack resize-animated <STACK_ID> <LEFT,TOP,RIGHT,BOTTOM>
    am stack resize-docked-stack <LEFT,TOP,RIGHT,BOTTOM> [<TASK_LEFT,TASK_TOP,TASK_RIGHT,TASK_BOTTOM>]
    am stack size-docked-stack-test: <STEP_SIZE> <l|t|r|b> [DELAY_MS]
    am stack move-top-activity-to-pinned-stack: <STACK_ID> <LEFT,TOP,RIGHT,BOTTOM>
    am stack positiontask <TASK_ID> <STACK_ID> <POSITION>
    am stack list
    am stack info <STACK_ID>
    am stack remove <STACK_ID>
    am task lock <TASK_ID>
    am task lock stop
    am task resizeable <TASK_ID> [0 (unresizeable) | 1 (crop_windows) | 2 (resizeable) | 3 (resizeable_and_pipable)]
    am task resize <TASK_ID> <LEFT,TOP,RIGHT,BOTTOM>
    am task drag-task-test <TASK_ID> <STEP_SIZE> [DELAY_MS]
    am task size-task-test <TASK_ID> <STEP_SIZE> [DELAY_MS]
    am get-config
    am suppress-resize-config-changes <true|false>
    am set-inactive [–user <USER_ID>] <PACKAGE> true|false
    am get-inactive [–user <USER_ID>] <PACKAGE>
    am send-trim-memory [–user <USER_ID>] <PROCESS>
    [HIDDEN|RUNNING_MODERATE|BACKGROUND|RUNNING_LOW|MODERATE|RUNNING_CRITICAL|COMPLETE]
    am get-current-user

    am start: start an Activity. Options are:
    -D: enable debugging
    -N: enable native debugging
    -W: wait for launch to complete
    –start-profiler <FILE>: start profiler and send results to <FILE>
    –sampling INTERVAL: use sample profiling with INTERVAL microseconds
    between samples (use with –start-profiler)
    -P <FILE>: like above, but profiling stops when app goes idle
    -R: repeat the activity launch <COUNT> times. Prior to each repeat,
    the top activity will be finished.
    -S: force stop the target app before starting the activity
    –track-allocation: enable tracking of object allocations
    –user <USER_ID> | current: Specify which user to run as; if not
    specified then run as the current user.
    –stack <STACK_ID>: Specify into which stack should the activity be put.
    am startservice: start a Service. Options are:
    –user <USER_ID> | current: Specify which user to run as; if not
    specified then run as the current user.

    am stopservice: stop a Service. Options are:
    –user <USER_ID> | current: Specify which user to run as; if not
    specified then run as the current user.

    am force-stop: force stop everything associated with <PACKAGE>.
    –user <USER_ID> | all | current: Specify user to force stop;
    all users if not specified.

    am kill: Kill all processes associated with <PACKAGE>. Only kills.
    processes that are safe to kill — that is, will not impact the user
    experience.
    –user <USER_ID> | all | current: Specify user whose processes to kill;
    all users if not specified.

    am kill-all: Kill all background processes.

    am broadcast: send a broadcast Intent. Options are:
    –user <USER_ID> | all | current: Specify which user to send to; if not
    specified then send to all users.
    –receiver-permission <PERMISSION>: Require receiver to hold permission.

    am instrument: start an Instrumentation. Typically this target <COMPONENT>
    is the form <TEST_PACKAGE>/<RUNNER_CLASS> or only <TEST_PACKAGE> if there
    is only one instrumentation. Options are:
    -r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT). Use with
    [-e perf true] to generate raw output for performance measurements.
    -e <NAME> <VALUE>: set argument <NAME> to <VALUE>. For test runners a
    common form is [-e <testrunner_flag> <value>[,<value>…]].
    -p <FILE>: write profiling data to <FILE>
    -w: wait for instrumentation to finish before returning. Required for
    test runners.
    –user <USER_ID> | current: Specify user instrumentation runs in;
    current user if not specified.
    –no-window-animation: turn off window animations while running.
    –abi <ABI>: Launch the instrumented process with the selected ABI.
    This assumes that the process supports the selected ABI.

    am trace-ipc: Trace IPC transactions.
    start: start tracing IPC transactions.
    stop: stop tracing IPC transactions and dump the results to file.
    –dump-file <FILE>: Specify the file the trace should be dumped to.

    am profile: start and stop profiler on a process. The given <PROCESS> argument
    may be either a process name or pid. Options are:
    –user <USER_ID> | current: When supplying a process name,
    specify user of process to profile; uses current user if not specified.

    am dumpheap: dump the heap of a process. The given <PROCESS> argument may
    be either a process name or pid. Options are:
    -n: dump native heap instead of managed heap
    –user <USER_ID> | current: When supplying a process name,
    specify user of process to dump; uses current user if not specified.

    am set-debug-app: set application <PACKAGE> to debug. Options are:
    -w: wait for debugger when application starts
    –persistent: retain this value

    am clear-debug-app: clear the previously set-debug-app.

    am set-watch-heap: start monitoring pss size of <PROCESS>, if it is at or
    above <HEAP-LIMIT> then a heap dump is collected for the user to report

    am clear-watch-heap: clear the previously set-watch-heap.

    am bug-report: request bug report generation; will launch a notification
    when done to select where it should be delivered. Options are:
    –progress: will launch a notification right away to show its progress.

    am monitor: start monitoring for crashes or ANRs.
    –gdb: start gdbserv on the given port at crash/ANR

    am hang: hang the system.
    –allow-restart: allow watchdog to perform normal system restart

    am restart: restart the user-space system.

    am idle-maintenance: perform idle maintenance now.

    am screen-compat: control screen compatibility mode of <PACKAGE>.

    am package-importance: print current importance of <PACKAGE>.

    am to-uri: print the given Intent specification as a URI.

    am to-intent-uri: print the given Intent specification as an intent: URI.

    am to-app-uri: print the given Intent specification as an android-app: URI.

    am switch-user: switch to put USER_ID in the foreground, starting
    execution of that user if it is currently stopped.

    am start-user: start USER_ID in background if it is currently stopped,
    use switch-user if you want to start the user in foreground.

    am stop-user: stop execution of USER_ID, not allowing it to run any
    code until a later explicit start or switch to it.
    -w: wait for stop-user to complete.
    -f: force stop even if there are related users that cannot be stopped.

    am stack start: start a new activity on <DISPLAY_ID> using <INTENT>.

    am stack movetask: move <TASK_ID> from its current stack to the top (true) or bottom (false) of <STACK_ID>.

    am stack resize: change <STACK_ID> size and position to <LEFT,TOP,RIGHT,BOTTOM>.

    am stack resize-docked-stack: change docked stack to <LEFT,TOP,RIGHT,BOTTOM>
    and supplying temporary different task bounds indicated by
    <TASK_LEFT,TOP,RIGHT,BOTTOM>

    am stack size-docked-stack-test: test command for sizing docked stack by
    <STEP_SIZE> increments from the side <l>eft, <t>op, <r>ight, or <b>ottom
    applying the optional [DELAY_MS] between each step.

    am stack move-top-activity-to-pinned-stack: moves the top activity from
    <STACK_ID> to the pinned stack using <LEFT,TOP,RIGHT,BOTTOM> for the
    bounds of the pinned stack.

    am stack positiontask: place <TASK_ID> in <STACK_ID> at <POSITION>
    am stack list: list all of the activity stacks and their sizes.

    am stack info: display the information about activity stack <STACK_ID>.

    am stack remove: remove stack <STACK_ID>.

    am task lock: bring <TASK_ID> to the front and don’t allow other tasks to run.

    am task lock stop: end the current task lock.

    am task resizeable: change resizeable mode of <TASK_ID>.
    0 (unresizeable) | 1 (crop_windows) | 2 (resizeable) | 3 (resizeable_and_pipable)

    am task resize: makes sure <TASK_ID> is in a stack with the specified bounds.
    Forces the task to be resizeable and creates a stack if no existing stack
    has the specified bounds.

    am task drag-task-test: test command for dragging/moving <TASK_ID> by
    <STEP_SIZE> increments around the screen applying the optional [DELAY_MS]
    between each step.

    am task size-task-test: test command for sizing <TASK_ID> by <STEP_SIZE> increments within the screen applying the optional [DELAY_MS] between
    each step.

    am get-config: retrieve the configuration and any recent configurations
    of the device.
    am suppress-resize-config-changes: suppresses configuration changes due to
    user resizing an activity/task.

    am set-inactive: sets the inactive state of an app.

    am get-inactive: returns the inactive state of an app.

    am send-trim-memory: send a memory trim event to a <PROCESS>.

    am get-current-user: returns id of the current foreground user.

    <INTENT> specifications include these flags and arguments:
    [-a <ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>]
    [-c <CATEGORY> [-c <CATEGORY>] …]
    [-e|–es <EXTRA_KEY> <EXTRA_STRING_VALUE> …]
    [–esn <EXTRA_KEY> …]
    [–ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE> …]
    [–ei <EXTRA_KEY> <EXTRA_INT_VALUE> …]
    [–el <EXTRA_KEY> <EXTRA_LONG_VALUE> …]
    [–ef <EXTRA_KEY> <EXTRA_FLOAT_VALUE> …]
    [–eu <EXTRA_KEY> <EXTRA_URI_VALUE> …]
    [–ecn <EXTRA_KEY> <EXTRA_COMPONENT_NAME_VALUE>]
    [–eia <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE…]]
    (mutiple extras passed as Integer[])
    [–eial <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE…]]
    (mutiple extras passed as List<Integer>)
    [–ela <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE…]]
    (mutiple extras passed as Long[])
    [–elal <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE…]]
    (mutiple extras passed as List<Long>)
    [–efa <EXTRA_KEY> <EXTRA_FLOAT_VALUE>[,<EXTRA_FLOAT_VALUE…]]
    (mutiple extras passed as Float[])
    [–efal <EXTRA_KEY> <EXTRA_FLOAT_VALUE>[,<EXTRA_FLOAT_VALUE…]]
    (mutiple extras passed as List<Float>)
    [–esa <EXTRA_KEY> <EXTRA_STRING_VALUE>[,<EXTRA_STRING_VALUE…]]
    (mutiple extras passed as String[]; to embed a comma into a string,
    escape it using “\,”)
    [–esal <EXTRA_KEY> <EXTRA_STRING_VALUE>[,<EXTRA_STRING_VALUE…]]
    (mutiple extras passed as List<String>; to embed a comma into a string,
    escape it using “\,”)
    [–f <FLAG>]
    [–grant-read-uri-permission] [–grant-write-uri-permission]
    [–grant-persistable-uri-permission] [–grant-prefix-uri-permission]
    [–debug-log-resolution] [–exclude-stopped-packages]
    [–include-stopped-packages]
    [–activity-brought-to-front] [–activity-clear-top]
    [–activity-clear-when-task-reset] [–activity-exclude-from-recents]
    [–activity-launched-from-history] [–activity-multiple-task]
    [–activity-no-animation] [–activity-no-history]
    [–activity-no-user-action] [–activity-previous-is-top]
    [–activity-reorder-to-front] [–activity-reset-task-if-needed]
    [–activity-single-top] [–activity-clear-task]
    [–activity-task-on-home]
    [–receiver-registered-only] [–receiver-replace-pending]
    [–receiver-foreground]
    [–selector]
    [<URI> | <PACKAGE> | <COMPONENT>]

    Error: Unknown component: jra.com.example.mateus.testeappkt/com.zeroturnaround.jrebel.android.agent.companion.CompanionStatusActivity

    Does anybody can help me, please?

    #62657

    Hannes Metssalu
    Rebel Staff

    Hey Mateus! We’re aware of the issue and are looking into it. Maybe you can temporarily use another ROM or emulator, since probably you’re using a custom ROM (LineageOS?). I’ll let you know as soon as we have any news.

    #62659

    Mateus M.
    Member

    Hi, Hannes Metssalu! I just checked my email and I read your answer.
    I didn’t know custom ROM could give me problems. In the meantime, I’ll use another emulator or device.

    Thank you!
    All the best.

    #64026

    Hannes Metssalu
    Rebel Staff

    I wanted to let you know that we’ve now added the support for LineageOS. It will be publicly available in our future releases.

    If there are any issues, let us know at android@zeroturnaround.com.

    #64040

    Mateus M.
    Member

    Hi Hannes,

    Thanks for supporting!

    Best regards.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.