connection Serenitywithcucmber to Appiumserver is failed

The problem

Hall all,
i write a automation test for an android app unsing serenitywithcucmber and appium server. I have by running the following error: net.thucydides.core.pages.WrongPageError: The page object class de.qa.appium.features.Pages.HomePage looks dodgy: Failed to instantiate page (net.thucydides.core.webdriver.UnsupportedDriverException: Could not instantiate class io.appium.java_client.AppiumDriver)
And my appiumserver do not get the capalitiy, that is wroten in serenity.properties.

Environment

• Appium version (or git revision) that exhibits the issue: 1.17
• Last Appium version that did not exhibit the issue (if applicable):
• Node.js version (unless using Appium.app|exe):
• Java version: jdk-11.0.6
• Mobile platform/version under test:
• Real device or emulator/simulator: Real device
• Appium CLI or Appium.app|exe: Appim App

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium logs

Code To Reproduce Issue [ Good To Have ]

This is my pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>de.mvise.qa.appium</groupId>
  <artifactId>AutomationTests</artifactId>
  <version>0.0.1-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>Toolbox</name>
  <url>http://maven.apache.org</url>

  <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <serenity.cucumber.version>1.9.31</serenity.cucumber.version>
    </properties>

    <dependencies>
        <dependency>
            <groupId>net.serenity-bdd</groupId>
            <artifactId>serenity-cucumber</artifactId>
            <version>${serenity.cucumber.version}</version>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
            <version>1.7.7</version>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.12</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.assertj</groupId>
            <artifactId>assertj-core</artifactId>
            <version>1.7.0</version>
        </dependency>
	</dependencies>
    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.18.1</version>
            </plugin>
            <plugin>
                <artifactId>maven-failsafe-plugin</artifactId>
                <version>2.18.1</version>
                <configuration>
                    <includes>
                        <include>**/*Test.java</include>
                        <include>**/*TestSuite.java</include>
                        <include>**/Test*.java</include>
                        <include>**/When*.java</include>
                    </includes>
                    <argLine>-Xmx512m</argLine>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>integration-test</goal>
                            <goal>verify</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.2</version>
                <configuration>
                    <source>1.8</source>
                    <target>1.8</target>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>

Start with the pom.xml and the reported WrongPageError while inspecting the HomePage/AppiumDriver instantiation path. Compare the reported Serenity Cucumber setup with the capabilities referenced in serenity.properties and reproduce the failure against Appium 1.17. Done means the cause of the missing capabilities or driver-instantiation failure is identified and a reproducible resolution is documented.