Application update is rejected by Google Play Store

My app update got rejected, from publishing in Play Store, without getting any further informations or explanation

Your app has been rejected and wasn’t published due to a policy
violation. If you submitted an update, the previous version of your
app is still available on Google Play.

FYI : I published a different application with the same UI/UX but different content in January 2020.

c# – How to organize database access logic for the infrastructure and application layer when avoiding ORM tools?

ORMs like Entity Framework do not preclude you from using Raw SQL queries.

If Entity Framework is a bit too much for your liking, consider using Dapper or any of a number of different micro-frameworks. These tools remove a lot of the hassle of making a connection to the database and managing query parameters without encountering Little Bobby Tables, allowing you to focus your time and effort on writing the SQL queries.

ORMs also serve as your Data Access Layer, abstracting CRUD operations away from the more interesting Service Layer of your application. If you still feel like writing your own Data Access Layer, you can still do so. You will need one class and four methods for each table in your database (Create, Read, Update & Delete).

The way you manage your connection can vary. Depending on how quickly MariaDB can open connections and whether or not it caches connections, you might want to just open a connection for each query. You could also do it at the Aggregate level if you’re practicing DDD. Or, you could simply open a connection and leave it open. It really all depends on your application and what you want to do with it.

One file per SQL statement sounds like a bit much. Try putting your SQL statements inside your entity classes; it’s a very convenient place to stash them.

Folder structures are largely a matter of taste. There’s no “standard,” and everyone does them differently.

Further Reading
P of EAA : Data Mapper
P of EAA : Repository
P of EAA : Service Layer

implement application for multiple users, starting with db

Hello, I wrote an texteditor with PHP,JS,mySQL that can extract data from JSON, write JSON files, display the update time etc.. I use 2 tabels in the db for ‘sections’ and ‘items’ (fields: headline / text) (1:n)

Now I want to implement this for multiple users.
I can write a log-in system using another table for the users, but then I stuff all the user data into these 2 tables.

I this is a common way to do this or are there better alternatives?


c# – When to publish domain events when handling transactions in the application service

This is something that has been bothering me for quite some time, I tried different approaches over the past year but I always come back to reflect on this, so I’ll throw myself out here !

So, first get some common ground: if we follow the blue book, transaction handling should be done in the application service. We open a transaction, retrieve 1 or multiple aggregates, only adapt 1 aggregate and commit that transaction. ( 1 aggregate per transaction ).

If we then follow the theory of domain events, it seems that we have 2 camps, the one publishing events before commiting, the one publishing events after commiting. I’m fine with the second one, so let’s stay in that context.

Ok I had different approaches on this one, I’ll explain them so you can judge by yourself or maybe find other alternatives.

I’m using .NET btw.

So my first attempt was quite easy, and is the one I’m still using now.

I have a generic repository with 2 methods, like this:

public interface IRepository<TId, T> where T : Aggregate
    T GetById(TId id);
    Save(T aggregate);

And in my save method I do a couple of things:

  • Check if the entity already exists, if not, add it, if it does exist, attach it back to the change tracker ( using E.F. Core for now, don’t focus on this part, it’s not important )
  • As we have only 1 aggregate per transaction, I decided to call my SaveChanges(); method, the one that commits the changes to the database if we don’t have a parent scope open, in the Save method of my repository. So I’m basically committing in my repository.
  • My aggregate base class holds a list of events that have occured from the moment we get it to the moment we save it. So after my save changes in this method, I basically retrieve the unpublished events of my aggregate, dispatch them, and clear the list.

As you can see, the Save method does quite a few things, maybe some considered outside of it’s responsability. But it has been quite a straight forward experience using this method, as my application services don’t really have transactions involved anymore, and each save commits a transaction.

The second approach for me consisted of overriding the .SaveChanges method of entity framework. I would basically retrieve the list of tracked aggregates, retrieve the events on them. Then call the base.SaveChanges() method that will actually commit, and then dispatch the events.

The repository save method in this case would only attach the entity to the change tracker when saving it ( I tend to retriev emy entities without change tracking and only track the changes on the .Save part, as it is possible to retrieve multiple entities in the same method for information purposes, but only 1 of them will be changed ).

What I then do is wrap my DbContext into a IUnitOfWork interface, like this

public interface IUnitOfWork
    void Commit();

And the commit method calls the context.SaveChanges(); method, which has been overriden to dispatch events after the commit.

My application service would then inject the repositories needed, call the .Save() method on one of them, and the commit the uow who is also injected.

The problem I have with those 2 is in the context of E.F., they are not always 100% correct for what I want to do.

If I open a transaction scope in my application service, both of those methods will actually publish events when saving on the repo / committing in the UoW, but if I rollback the parent transaction scope, I will have an invalid state.

My ultimate goal would be to always use a transaction scope in my application service, using that transaction scope’s commit to actually commit the changes instead of the context’s .SaveChanges() method, and only dispatch the events after the transaction scope is committed.

Now, my question(s) is(are): does the 2 first approaches seem correct to you, and am I to worried about small details ? Is my third idea actually achievable in a correct way ? Do I maybe miss an extra alternative ?

Thanks you !

software distribution – how to distribute an application that needs an api key to work

I am trying to distribute a project that makes requests from an external API. My only problem is that I need to use a secret key to make an API request. My program is entirely on the client side, so how can I distribute it without needing a server in the middle to handle the program requests to the specific API.

sharepoint online – Application Customizer to hide Save button

I am trying to create application customizer to hide save and cancel button from Newform.aspx in Modern UI , i tried writing below code but everything getting hide instead of Save button noticed html is getting display:none

    enter code here  

      public onInit(): Promise<void> {
        var Libraryurl = this.context.pageContext.list.title;  , `Initialized ${strings.Title}`);
       // this.context.placeholderProvider.changedEvent.add(this, this._renderPlaceHolders);  

        let message: string =;
        if (!message) {
          message = '(No properties were provided.)';

        //Dialog.alert(`Hello from ${strings.Title}:nn${message}`);  
        // code to hide button
            let newbutton: any = document.getElementsByName("Save")(0) || document.documentElement;  
           // let newbutton2: any = document.getElementsByName("Cancel")(1) || document.documentElement; 
            //let newbutton3: any = document.getElementsByName("Edit columns")(2) || document.documentElement;  

   = "none"; 
            // = "none"; 
            return Promise.resolve();

            // = "none"; 

       // this._renderPlaceHolders();

        //return Promise.resolve();

enter image description here

Design inputs for XML based java application

I have a java application which basically has to do 1 thing.
Read a large xml, extract information from it, and send the information to another system but in a different xml format.

Earlier we were using jaxb to convert it to a relational database and then use jaxb again to convert it to the desired xml, but given the increasing size of the XMLs, we have to implement a fragmented reading approach using a combination of sax parsing and jaxb so that the memory usage stays within the accepted limits.
But this has slowed down the application considerably. I know there are always tradeoffs, but could anyone please provide any design inputs on the below:

Would it make sense to

  • use something like an XML database instead of the relational one
  • store the xml as is and instead use apache Lucene or Solr to index it and make it searchable

Any other recommendations are welcome. Please let me know if any more information is needed.

Contest – Application Icons – 5 Total

Hello, we are looking for application icons for our web app. We have 5 applications, and they are all related to Keyboard/Typing Instruction:

Keyboarding for Kids
— Elementary Level Program

Keyboard Mastery
— Middle School -> Adult Level Program
Keyboard Short Course
— Same as Keyboard Mastery, but shorter

Skillbuilding Mastery
— Advanced version of Keyboard Mastery

Ten Key Mastery
— Number Pad Program for Middle School+

We would like all the icons (EXCEPT Keyboarding for Kids) to have a similar look and feel. Attached are the current icons. We like them, but they are definitely outdated (colors, square shape, font, graphics).


The contest will run through May 25th. We can provide feedback if requested. We will be paying $25/icon, so $125 total if you are chosen with all icons.


Script that allows you to install the application, run it and uninstall it after use

I have an Android 4.2.1 tablet with Link2SD installed, but I have a memory problem. I already looked on the internet and didn’t find it. I would like to find a script or application that would automatically allow you to install an apk and uninstall it after use. Can someone help me?

seo – Is server side rendering without any styling acceptable for a single page application (that is heavily styled) in order to satisfy most search bots?

Let’s say that you have a big / heavy single page application (SPA) that can be represented statically in 100,000+ pages.

Will it be acceptable to have a back-end that dynamically generates pages that are very similar in structure and content to the pages generated by the SPA but with no styling – i.e generating a craigslist-like version of the SPA just for the search engines.

Will it be considered cloaking or will it be okay? (Given that the routing will the same and the structure and the content of the pages will be 95%+ similar to the structure and the content of the SPA)

The reason for me thinking about this approach is that it will save both a lot of development time (in this particular scenario … because otherwise styling inconsistencies have to be handled) and unimaginable (in this particular scenario) amount of computational resources (that otherwise would be needed to cache everything using headless chromium).